From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: GPL-only symbol Error
Date: Tue, 22 Nov 2011 16:51:57 -0800 [thread overview]
Message-ID: <20111123005157.GA18850@kroah.com> (raw)
In-Reply-To: <6F5DE7538AFCDA45A114F5E7510424A702D3E42D@hq-exchange01.bytemobile.com>
On Tue, Nov 22, 2011 at 04:34:21PM -0800, Jeff Haran wrote:
> Just curious, can you provide links to these cases?
No kernel cases ever became public, but the SAMBA team have lots of
public cases where they have successfully handled this type of case.
> I've read the COPYING file at the top of the Linux source tree. I am not
> a lawyer, but I don't see anything in it that would prohibit somebody
> from taking the GPL kernel sources, changing the EXPORT_SYMBOL_GPL()s to
> EXPORT_SYMBOL()s, publishing that modified kernel source as required by
> the GPL license but then keep their module source that uses the now
> non-GPL symbols private. It seems like it should be prohibited in the
> spirit of open source, but I don't see any mention of these symbol
> declarations in the license.
The license does not say anything about this, nor should it.
thanks,
greg k-h
next prev parent reply other threads:[~2011-11-23 0:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 21:48 GPL-only symbol Error Sengottuvelan S
2011-11-22 21:53 ` Jeff Haran
2011-11-22 22:08 ` Sengottuvelan S
2011-11-22 22:34 ` Greg KH
2011-11-22 22:35 ` Jeff Haran
2011-11-22 22:44 ` Greg KH
2011-11-23 0:34 ` Jeff Haran
2011-11-23 0:51 ` Greg KH [this message]
2011-11-23 1:09 ` Graeme Russ
2011-11-23 1:21 ` Jeff Haran
2011-11-23 1:39 ` Guillaume Knispel
2011-11-23 2:10 ` Jeff Haran
2011-11-23 2:50 ` Greg KH
2011-11-23 18:05 ` Jeff Haran
2011-11-23 19:32 ` Greg KH
2011-11-23 1:56 ` Greg Freemyer
2011-11-23 2:17 ` Jeff Haran
2011-11-23 2:48 ` Greg KH
[not found] ` <1322045488.28603.17.camel@thorin>
2011-11-23 18:31 ` Jeff Haran
2011-11-23 19:28 ` Greg KH
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=20111123005157.GA18850@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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.