From: "Arend van Spriel" <arend@broadcom.com>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Keith Packard" <keithp@keithp.com>,
"Ralf Baechle" <ralf@linux-mips.org>,
"David Woodhouse" <dwmw2@infradead.org>,
"Stephen Hemminger" <shemminger@vyatta.com>,
"John W. Linville" <linville@tuxdriver.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Ted Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH] module: Clarify GPL-Compatible is OK
Date: Sun, 8 Apr 2012 14:42:24 +0200 [thread overview]
Message-ID: <4F8187B0.1000804@broadcom.com> (raw)
In-Reply-To: <CAB=NE6Uf2cvhLcS4+Nu4j0DvorOZJJR1pWOKteTbQuHan07nng@mail.gmail.com>
On 04/07/2012 03:02 AM, Luis R. Rodriguez wrote:
> On Fri, Apr 6, 2012 at 5:51 PM, Luis R. Rodriguez<mcgrof@frijolero.org> wrote:
>
>> 4) Use the patch and leave it to the person who wants to extract code
>> to figure out the exact module license.
>
> After some though I think this is the only approach possible. Consider
> ath5k which has files under difference licenses:
>
> * Dual BSD/GPL
> * GPL
> * ISC
>
> The person taking code must check the header of each file.
>
> Luis
I would say that regardless your patch the "your preferred adjective"
license disclaimer in the source files trumps any MODULE_LICENSE value
so checking the files is always a necessary step. It is the only place
to look for the specific license information and it is on a per-file
basis as stated above. MODULE_LICENSE clearly groups these so a
generalization seems justified just for that.
So MODULE_LICENSE is really just about allowing EXPORT_SYMBOL_GPL or
not. I admit that statement does not cover everything as the
MODULE_LICENSE is part of the module information, but as said it may or
may not cover a number of different licenses used within the module.
So this specific macro does not, or even should not, help people figure
out the license. We could consider some other tagging of each and every
source file and add some scripting support to do the task, but that will
be one hell of a patch so I will forever deny suggesting it ;-)
Gr. AvS
next prev parent reply other threads:[~2012-04-08 12:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 0:11 [PATCH] module: Clarify GPL-Compatible is OK Luis R. Rodriguez
2012-04-07 0:27 ` Greg Kroah-Hartman
2012-04-07 0:28 ` Al Viro
2012-04-07 0:57 ` Luis R. Rodriguez
2012-04-07 0:36 ` Linus Torvalds
2012-04-07 0:51 ` Luis R. Rodriguez
2012-04-07 1:02 ` Luis R. Rodriguez
2012-04-08 12:42 ` Arend van Spriel [this message]
2012-04-07 2:49 ` Ted Ts'o
2012-04-07 3:01 ` Luis R. Rodriguez
2012-04-07 21:15 ` Ted Ts'o
2012-04-08 0:52 ` Luis R. Rodriguez
2012-04-08 14:57 ` Alan Cox
2012-04-08 16:06 ` Luis R. Rodriguez
2012-04-08 17:12 ` Alan Cox
2012-04-08 20:23 ` Ted Ts'o
2012-04-07 19:03 ` Alan Cox
2012-04-08 12:49 ` Arend van Spriel
2012-04-08 22:50 ` Dan Williams
2012-05-07 2:39 ` Rusty Russell
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=4F8187B0.1000804@broadcom.com \
--to=arend@broadcom.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@frijolero.org \
--cc=ralf@linux-mips.org \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@vyatta.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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.