From: Rob Landley <rob@landley.net>
To: Joe Perches <joe@perches.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Richard Yao <ryao@gentoo.org>,
chanho.min@lge.com,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Why are BSD-licensed LZ4 symbols GPL exported?
Date: Tue, 20 Aug 2013 16:37:49 -0500 [thread overview]
Message-ID: <1377034669.2737.83@driftwood> (raw)
In-Reply-To: <1377020294.2016.51.camel@joe-AO722> (from joe@perches.com on Tue Aug 20 12:38:14 2013)
On 08/20/2013 12:38:14 PM, Joe Perches wrote:
> On Tue, 2013-08-20 at 18:11 +0100, Matthew Garrett wrote:
> > On Thu, Aug 15, 2013 at 10:19:56PM -0400, Richard Yao wrote:
> > > Why are the LZ4 symbols being GPL-exported when the LZ4 code is
> > > BSD-licensed and no substantial changes appear to have been made
> when it
> > > was merged?
> >
> > EXPORT_SYMBOL_GPL is intended an indication that using a symbol is
> > likely to result in you producing a derived work of the kernel, and
> the
> > kernel as a whole is under the GPL. It has nothing to do with
> additional
> > licenses that individual pieces of code may be available under.
>
> Maybe not.
>
> http://www.ifross.org/en/artikel/ongoing-dispute-over-value-exportsymbolgpl-function
Kernel developers: "We're making symbols that we, as the creators of
this project, don't think you can use without the result being a
derived work".
Lawyers: "we're prepared to argue over the definitions of 'that', 'as',
'of', 'this', 'use', and 'the', as long as we're paid by the hour."
This random speculation outside of a courtroom actually capable of
setting precedent strikes you as relevant for what reason?
Rob
next prev parent reply other threads:[~2013-08-20 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 2:19 Why are BSD-licensed LZ4 symbols GPL exported? Richard Yao
2013-08-16 21:45 ` [PATCH] Correct the LZ4 license Richard Laager
2013-08-17 1:24 ` Kyungsik Lee
2013-08-20 17:11 ` Why are BSD-licensed LZ4 symbols GPL exported? Matthew Garrett
2013-08-20 17:38 ` Joe Perches
2013-08-20 21:37 ` Rob Landley [this message]
2013-08-20 21:46 ` Joe Perches
2013-08-20 22:07 ` Joe Perches
2013-08-20 22:33 ` Matthew Garrett
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=1377034669.2737.83@driftwood \
--to=rob@landley.net \
--cc=chanho.min@lge.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=ryao@gentoo.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 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.