From: Jonathan Corbet <corbet@lwn.net>
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>,
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, 6 Feb 2019 17:21:51 -0700 [thread overview]
Message-ID: <20190206172151.56fcce6c@lwn.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1901291510060.1513@nanos.tec.linutronix.de>
On Tue, 29 Jan 2019 15:11:40 +0100 (CET)
Thomas Gleixner <tglx@linutronix.de> wrote:
> On Tue, 29 Jan 2019, Jessica Yu wrote:
> > +++ Thomas Gleixner [28/01/19 23:38 +0100]:
> > > + "GPL" Module is licensed under GPL version 2. This
> > > + does not express any distinction between
> > > + GPL-2.0-only or GPL-2.0-or-later. The exact
> > > + license information can only be determined
> > > + via the license information in the
> > > + corresponding source files.
> > > +
> > > + "GPL v2" Same as "GPL v2". It exists for historic
> > > + reasons.
> >
> > Did you mean to say 'Same as "GPL"' here? (as in, "GPL v2" conveys the same
> > information as the "GPL" module license string)
>
> Of course. After staring at all this for too long I confused myself and did
> not spot it even if I read through the whole thing several times.
Were you thinking of sending a new version with tweaks? I can happy apply
this version with this fix if you prefer, let me know...
Thanks,
jon
next prev parent reply other threads:[~2019-02-07 0:21 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
2019-01-30 21:47 ` Thomas Gleixner
2019-02-07 0:21 ` Jonathan Corbet [this message]
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=20190206172151.56fcce6c@lwn.net \
--to=corbet@lwn.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.