From: Greg KH <greg@kroah.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
devel@linuxdriverproject.org,
Jouni Malinen <jouni.malinen@atheros.com>,
ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/4] ath9k: move hw code to its own module
Date: Sat, 26 Sep 2009 08:45:49 -0700 [thread overview]
Message-ID: <20090926154549.GA4431@kroah.com> (raw)
In-Reply-To: <200909261404.54906.chunkeey@googlemail.com>
On Sat, Sep 26, 2009 at 02:04:54PM +0200, Christian Lamparter wrote:
> On Thursday 24 September 2009 05:07:00 Luis R. Rodriguez wrote:
> > hw code for Atheros 802.11n hardware is commmon between
> > different chipsets. This moves this code into a separate
> > module, the next expected user of this code will be
> > the ath9k_htc module.
> >
> > The ath9k/ dir is now selected by ATH9K_HW, an option which
> > gets selected by either ath9k or ath9k_htc, but remains
> > invisible for user menuconfig configuration. If either
> > ath9k or ath9k_htc will be compiled into the kernel
> > ath9k_hw will also be compiled in.
> >
> > diff --git a/drivers/net/wireless/ath/ath9k/hw.c b/drivers/net/wireless/ath/ath9k/hw.c
> > index 7a4de3d..7d167a1 100644
> > --- a/drivers/net/wireless/ath/ath9k/hw.c
> > +++ b/drivers/net/wireless/ath/ath9k/hw.c
> > @@ -33,6 +33,23 @@ static u32 ath9k_hw_ini_fixup(struct ath_hw *ah,
> > static void ath9k_hw_9280_spur_mitigate(struct ath_hw *ah, struct ath9k_channel *chan);
> > static void ath9k_hw_spur_mitigate(struct ath_hw *ah, struct ath9k_channel *chan);
> >
> > +MODULE_AUTHOR("Atheros Communications");
> [...]
> > +
> > +static int __init ath9k_init(void)
> > +{
> > + return 0;
> > +}
> > +module_init(ath9k_init);
> > +
> > +static void __exit ath9k_exit(void)
> > +{
> > + return;
> > +}
> > +module_exit(ath9k_exit);
> > +
> > /********************/
> > /* Helper Functions */
> > /********************/
>
> FYI: there's no need for module_init/module_exit stubs.
> ( http://osdir.com/ml/linux-wireless/2009-04/msg00478.html )
But it's nicer if they are there, I'd recommend keeping them.
thanks,
greg k-h
next prev parent reply other threads:[~2009-09-26 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 3:06 [PATCH 0/4] atheros: move ath9k hw code to a module Luis R. Rodriguez
2009-09-24 3:06 ` [PATCH 1/4] ath9k: use common read/write ops on pci and debug code Luis R. Rodriguez
2009-09-24 3:07 ` [PATCH 2/4] ath9k: move hw code to its own module Luis R. Rodriguez
2009-09-26 12:04 ` Christian Lamparter
2009-09-26 15:45 ` Greg KH [this message]
2009-09-24 3:07 ` [PATCH 3/4] ath9k_hw: print device ID if not supported Luis R. Rodriguez
2009-09-24 3:07 ` [PATCH 4/4] ath9k_hw: add AR9271 srev and device ID to allow hw to support ar9271 Luis R. Rodriguez
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=20090926154549.GA4431@kroah.com \
--to=greg@kroah.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=chunkeey@googlemail.com \
--cc=devel@linuxdriverproject.org \
--cc=jouni.malinen@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).