From: "Arend van Spriel" <arend@broadcom.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Luis R. Rodriguez" <mcgrof@frijolero.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] compat: makes all compat symbols EXPORT_SYMBOL_GPL()
Date: Mon, 5 Mar 2012 10:39:58 +0100 [thread overview]
Message-ID: <4F5489EE.20203@broadcom.com> (raw)
In-Reply-To: <20120303161537.0b4ac739@pyramind.ukuu.org.uk>
On 03/03/2012 05:15 PM, Alan Cox wrote:
>> Some of the modules in this patch are dual-licensed. I was under the
>> impression that EXPORT_SYMBOL_GPL was specifically for GPL-only code
>> although I could not find any specifics in the Documentation folder. Do
>> you (or someone else) have a reference on this topic?
>
> If your code is licensed GPL or greater rights then you shouldn't have a
> problem. The module loader recognizes
>
> "GPL"
> "GPL v2"
> "GPL and additional rights"
> "Dual BSD/GPL"
> "Dual MIT/GPL"
> "DUal MPL/GPL"
>
> as legitimate users of _GPL. Any work which is derivative of the kernel
> (which in practise I suspect means almost any module) will need a GPL
> compatible licence anyway.
>
Hi, Alan
I found the list above in module.h, but was not sure whether it was ok
to use _GPL for dual license. Thanks for clarifying this.
Gr. AvS
prev parent reply other threads:[~2012-03-05 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 23:08 [PATCH] compat: makes all compat symbols EXPORT_SYMBOL_GPL() Luis R. Rodriguez
2012-03-03 12:52 ` Arend van Spriel
2012-03-03 16:15 ` Alan Cox
2012-03-05 9:39 ` Arend van Spriel [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=4F5489EE.20203@broadcom.com \
--to=arend@broadcom.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.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 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).