From: Michael Buesch <mb@bu3sch.de>
To: "Jouni Malinen" <jkm@devicescape.com>
Cc: Dan Williams <dcbw@redhat.com>,
"John W. Linville" <linville@tuxdriver.com>,
Larry Finger <larry.finger@lwfinger.net>,
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 loggingconditional on IEEE80211_DEBUG_DROP
Date: Tue, 17 Apr 2007 22:40:43 +0200 [thread overview]
Message-ID: <200704172240.43792.mb@bu3sch.de> (raw)
In-Reply-To: <20070417154146.GA22909@devicescape.com>
On Tuesday 17 April 2007 17:41, Jouni Malinen wrote:
> My personal view on this _GPL in exports is that it is just unnecessary
> extra complexity in the implementation and there should not be any place
> for license enforcement in the kernel implementation; this is better
> left for the license text and things completely outside the source code.
> As such, I have a preference of not seeing _GPL added to code that is
> derived from anything I've written.
I clearly second that opinion and I thought we (the main people working
on wireless) had decided to _not_ use GPL syms in mac80211 (was d80211).
In my opinion license policy should not be represented in sourcecode.
Source is source, license is license. That are two absolutely seperate
things to me. For example, if I want to relicense some code (as
a copyright holder), I clearly don't want to change sourcecode for this.
In fact, I think the GPL suffix is pretty much useless, legal wise.
And everybody knows that the kernel is GPLed. So _every_ single symbol
is actually a _GPL() symbol. the _GPL() annotation is just redundant
and bloats code.
Using kernel syms from a non-GPL compatible module is always walking
a borderline. Be it for _GPL() or normal syms; Exactly the same issue
for both.
All IMO, of course. I'm perfectly aware of different people having
different opinions on this. ;)
--
Greetings Michael.
prev parent reply other threads:[~2007-04-17 20:42 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
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 [this message]
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=200704172240.43792.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=dcbw@redhat.com \
--cc=jkm@devicescape.com \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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).