From: Dan Williams <dcbw@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Larry Finger <larry.finger@lwfinger.net>,
Michael Buesch <mb@bu3sch.de>, Andreas Schwab <schwab@suse.de>,
linux-wireless@vger.kernel.org, Bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH] ieee80211-crypt: Make some TKIP and CCMP error logging conditional on IEEE80211_DEBUG_DROP
Date: Tue, 17 Apr 2007 10:25:08 -0400 [thread overview]
Message-ID: <1176819909.26202.33.camel@localhost.localdomain> (raw)
In-Reply-To: <20070417131222.GA8633@tuxdriver.com>
On Tue, 2007-04-17 at 09:12 -0400, John W. Linville wrote:
> On Mon, Apr 16, 2007 at 07:24:14PM -0500, Larry Finger wrote:
> > Michael Buesch wrote:
> > > On Monday 16 April 2007 20:50, Larry Finger wrote:
>
> > >> @@ -229,6 +229,7 @@ void free_ieee80211(struct net_device *d
> > >>
> > >> static int debug = 0;
> > >> u32 ieee80211_debug_level = 0;
> > >> +EXPORT_SYMBOL_GPL(ieee80211_debug_level);
> > >
> > > We don't use the _GPL suffix in mac80211.
> >
> > Upon inspection, neither does most of ieee80211. It is now changed.
>
> You are strongly encouraged to use the _GPL version for new symbol
> exports, especially those which are fundamentally internal to
> in-kernel subsystems and/or have no reasonable usage by drivers.
> FWIW, this symbol would seem to fulfill both of those criteria.
>
> If you do not object, I would prefer the _GPL version of the patch.
What's the rationale for mac80211 _not_ using _GPL exports? I thought
most new exports were pretty much required to be _GPL (otherwise
somebody would NAK it) unless it was really, really necessary that they
weren't.
Dan
next prev parent reply other threads:[~2007-04-17 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 16:24 [PATCH] ieee80211-crypt: Make some TKIP and CCMP error logging conditional on IEEE80211_DEBUG_DROP Larry Finger
2007-04-16 18:05 ` Andreas Schwab
2007-04-16 18:50 ` Larry Finger
2007-04-16 20:37 ` Michael Buesch
2007-04-17 0:24 ` Larry Finger
2007-04-17 13:12 ` John W. Linville
2007-04-17 14:25 ` Dan Williams [this message]
2007-04-17 15:21 ` John W. Linville
2007-04-17 18:49 ` Dan Williams
2007-04-17 15:41 ` [PATCH] ieee80211-crypt: Make some TKIP and CCMP error loggingconditional " Jouni Malinen
2007-04-17 20:40 ` Michael Buesch
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=1176819909.26202.33.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=schwab@suse.de \
/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).