[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.02.1105232116140.3078@ionos>
Date: Mon, 23 May 2011 21:17:39 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: KY Srinivasan <kys@...rosoft.com>
cc: "gregkh@...e.de" <gregkh@...e.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"johnstul@...ibm.com" <johnstul@...ibm.com>,
"hch@...radead.org" <hch@...radead.org>,
Hank Janssen <hjanssen@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>
Subject: RE: [PATCH 1/1] Clocksource: Move the Hyper-V clocksource driver
out of staging
On Mon, 23 May 2011, KY Srinivasan wrote:
> > > +module_init(init_hv_clocksource);
> > > +MODULE_DESCRIPTION("HyperV based clocksource");
> > > +MODULE_AUTHOR("K. Y. Srinivasan <ksrinivasan@...ell.com>");
> > > +MODULE_LICENSE("GPL");
> >
> > Why do we need to build this as a module?
>
> No particular reason. This is the way, I had it in the staging directory.
> Do you want me to build this as part of the kernel? I would then not have
> to worry about auto-loading issues.
If we get rid of the DMI/PCI stuff then the whole module code is
larger than the real code. So no point in building it modular, just
make it depend on CONFIG_WHATEVER_MEANS_HYPERV
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists