From: Harald Welte <laforge@gpl-violations.org>
To: Armijn Hemel <armijn@gpl-violations.org>
Cc: Sebastian Gottschall <s.gottschall@newmedia-net.de>,
linux-kernel@vger.kernel.org,
James Morris <jmorris@intercode.com.au>,
David Miller <davem@davemloft.net>,
Herbert Xu <herbert@gondor.hengli.com.au>
Subject: Re: changing EXPORT_SYMBOL_GPL to EXPORT_SYMBOL in DD-WRT
Date: Thu, 3 Mar 2011 16:23:49 +0100 [thread overview]
Message-ID: <20110303152349.GL8117@prithivi.gnumonks.org> (raw)
In-Reply-To: <1299164159.10725.19.camel@hibbert>
Hi Sebastian, Armijn and others,
I can only follow what Armijn has been writing.
On Thu, Mar 03, 2011 at 03:55:59PM +0100, Armijn Hemel wrote:
> I noticed that a few hours ago you changed a few lines in the kernel
> source of DD-WRT, changing the export from a few symbols from 'GPL only'
> to something a lot more permissive:
While the ideas and thoughts regarding the legal implications of
EXPORT_SYMBOL_GPL are wide (see e.g. http://lwn.net/Articles/154602/) and there
is no precedent as far as I know, there seems general consensus that it _at
least_ signifies the explicit intent of the author.
By using the _GPL variant, the author unmistakingly indicates:
"I consider any use of that symbol to create a derivative work which must again
be licensed under GNU GPL"
So by modifying a _GPL symbol into the non-GPL variant (and using the code from
a non-GPL module), one would clearly violate the intent of the original author.
Whether or not that intent of the author is grounded in copyright law may
depend on the specific jurisdiction, circumstances and the judge that would
make up his mind about it, if such a case ever went to court.
I would be interested to hear what DaveM, James Morris and Herbert Xu
as the authors of the files in question have to say about such activity.
Regards,
Harald
--
- Harald Welte <laforge@gpl-violations.org> http://gpl-violations.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
next prev parent reply other threads:[~2011-03-03 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 14:55 Armijn Hemel
2011-03-03 15:23 ` Harald Welte [this message]
[not found] ` <4D6FCA08.1080705@dd-wrt.com>
2011-03-03 18:07 ` Christian Scheele
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=20110303152349.GL8117@prithivi.gnumonks.org \
--to=laforge@gpl-violations.org \
--cc=armijn@gpl-violations.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=jmorris@intercode.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=s.gottschall@newmedia-net.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
all inboxes | Powered by JetHome®