From: Alan Cox <alan@llwyncelyn.cymru>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jessica Yu <jeyu@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Rusty Russell <rusty@rustcorp.com.au>,
Christoph Hellwig <hch@lst.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>
Subject: Re: [PATCH][RFC] module: Cure the MODULE_LICENSE "GPL" vs. "GPL v2" bogosity
Date: Wed, 30 Jan 2019 20:48:48 +0000 [thread overview]
Message-ID: <20190130204848.19fc6912@alans-desktop> (raw)
In-Reply-To: <alpine.DEB.2.21.1901291510060.1513@nanos.tec.linutronix.de>
> > > + "GPL and additional rights" Historical variant of expressing that the
> > > + module source is dual licensed under a
> > > + GPL v2 variant and MIT license. Please do
> > > + not use in new code.
Actually it was a historic fix for the fact that some slimeballs were
going to use a proposed "BSD" tag and just ship binaries only whilst
claiming that they were totally compliant with the BSD licence.
Alan
next prev parent reply other threads:[~2019-01-30 21:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 22:38 [PATCH][RFC] module: Cure the MODULE_LICENSE "GPL" vs. "GPL v2" bogosity Thomas Gleixner
2019-01-29 1:32 ` Joe Perches
2019-01-29 5:27 ` Greg KH
2019-01-29 13:06 ` Jessica Yu
2019-01-29 14:11 ` Thomas Gleixner
2019-01-30 20:48 ` Alan Cox [this message]
2019-01-30 21:47 ` Thomas Gleixner
2019-02-07 0:21 ` Jonathan Corbet
2019-02-08 16:02 ` [PATCH v2] " Thomas Gleixner
2019-02-09 9:37 ` Philippe Ombredanne
2019-02-09 12:11 ` Greg KH
2019-02-10 18:58 ` Thomas Gleixner
2019-02-11 15:19 ` Jonathan Corbet
2019-02-11 8:44 ` Jessica Yu
2019-01-30 5:01 ` [PATCH][RFC] " Rusty Russell
2019-01-30 18:21 ` Thomas Gleixner
2019-01-30 20:45 ` Alan Cox
2019-01-30 22:00 ` Thomas Gleixner
2019-01-31 15:18 ` Philippe Ombredanne
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=20190130204848.19fc6912@alans-desktop \
--to=alan@llwyncelyn.cymru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jeyu@kernel.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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