From: Thomas Gleixner <tglx@linutronix.de>
To: KY Srinivasan <kys@microsoft.com>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"johnstul@us.ibm.com" <johnstul@us.ibm.com>,
"hch@infradead.org" <hch@infradead.org>,
Hank Janssen <hjanssen@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: RE: [PATCH 1/1] Clocksource: Move the Hyper-V clocksource driver out of staging
Date: Mon, 23 May 2011 21:17:39 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1105232116140.3078@ionos> (raw)
In-Reply-To: <6E21E5352C11B742B20C142EB499E0481FC8D4@TK5EX14MBXC122.redmond.corp.microsoft.com>
On Mon, 23 May 2011, KY Srinivasan wrote:
> > > +module_init(init_hv_clocksource);
> > > +MODULE_DESCRIPTION("HyperV based clocksource");
> > > +MODULE_AUTHOR("K. Y. Srinivasan <ksrinivasan@novell.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
next prev parent reply other threads:[~2011-05-23 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 17:12 [PATCH 1/1] Clocksource: Move the Hyper-V clocksource driver out of staging K. Y. Srinivasan
2011-05-23 18:15 ` Thomas Gleixner
2011-05-23 18:50 ` KY Srinivasan
2011-05-23 19:17 ` Thomas Gleixner [this message]
2011-05-23 18:40 ` john stultz
2011-05-23 18:43 ` KY Srinivasan
2011-05-23 18:42 ` Christoph Hellwig
2011-05-23 19:05 ` KY Srinivasan
-- strict thread matches above, loose matches on Subject: below --
2011-05-24 21:32 K. Y. Srinivasan
2011-05-24 22:43 ` Thomas Gleixner
2011-05-25 0:29 ` KY Srinivasan
2011-05-25 6:58 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.02.1105232116140.3078@ionos \
--to=tglx@linutronix.de \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=hch@infradead.org \
--cc=hjanssen@microsoft.com \
--cc=johnstul@us.ibm.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.