linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Chris Friesen <chris.friesen@genband.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: MODULE_LICENSE("GPL")??
Date: Fri, 03 Aug 2012 10:10:54 -0400	[thread overview]
Message-ID: <501BDBEE.60305@cfl.rr.com> (raw)
In-Reply-To: <20120803142923.311c70b6@pyramind.ukuu.org.uk>

On 08/03/2012 09:29 AM, Alan Cox wrote:
>> assumption that that actually meant they were NOT using GPL symbols.
>
> All symbols in the Linux kernel are to GPL code and all linking dynamic
> or otherwise is subject to the GPL licence. That is you need to be able
> to show anything non-free linked with it such as a kernel module is not a
> derivative work.

Why then is there EXPORT_SYMBOL_GPL and EXPORT_SYMBOL? As long as you have 
them both, one can and will, assume that what you say above is not the intent.

Again, our Linux kernel drivers are and always were GPL and at least partly 
so because of EXPORT_SYMBOL_GPL.

Mark





  reply	other threads:[~2012-08-03 14:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 21:24 MODULE_LICENSE("GPL")?? Mark Hounschell
2012-08-01 21:42 ` MODULE_LICENSE("GPL")?? Chris Friesen
2012-08-01 21:43 ` MODULE_LICENSE("GPL")?? Alan Cox
2012-08-02 12:19   ` MODULE_LICENSE("GPL")?? Mark Hounschell
2012-08-03  5:10     ` MODULE_LICENSE("GPL")?? Chris Friesen
2012-08-03 12:04       ` MODULE_LICENSE("GPL")?? Mark Hounschell
2012-08-03 13:29         ` MODULE_LICENSE("GPL")?? Alan Cox
2012-08-03 14:10           ` Mark Hounschell [this message]
2012-08-03 14:20             ` MODULE_LICENSE("GPL")?? Alan Cox
2012-08-03 18:19             ` MODULE_LICENSE("GPL")?? Theodore Ts'o

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=501BDBEE.60305@cfl.rr.com \
    --to=dmarkh@cfl.rr.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=chris.friesen@genband.com \
    --cc=linux-kernel@vger.kernel.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).