From: Joe Perches <joe@perches.com>
To: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>, Jessica Yu <jeyu@kernel.org>,
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: Mon, 28 Jan 2019 17:32:42 -0800 [thread overview]
Message-ID: <9d085583a1d9a1068838f4333a2f12156f77d246.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1901282105450.1669@nanos.tec.linutronix.de>
On Mon, 2019-01-28 at 23:38 +0100, Thomas Gleixner wrote:
> Therefore remove the well meant, but ill defined, distinction between "GPL"
> and "GPL v2" and document that:
>
> - "GPL" and "GPL v2" both express that the module is licensed under GPLv2
> (without a distinction of 'only' and 'or later') and is therefore kernel
> license compliant.
>
> - None of the MODULE_LICENSE strings can be used for expressing or
> determining the exact license
>
> - Their sole purpose is to decide whether the module is free software or
> not.
Thanks Thomas.
Acked-by: Joe Perches <joe@perches.com>
if you want that.
next prev parent reply other threads:[~2019-01-29 1:32 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 [this message]
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
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=9d085583a1d9a1068838f4333a2f12156f77d246.camel@perches.com \
--to=joe@perches.com \
--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;
as well as URLs for NNTP newsgroup(s).