[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190206172151.56fcce6c@lwn.net>
Date: Wed, 6 Feb 2019 17:21:51 -0700
From: Jonathan Corbet <corbet@....net>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Jessica Yu <jeyu@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg KH <gregkh@...uxfoundation.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Rusty Russell <rusty@...tcorp.com.au>,
Christoph Hellwig <hch@....de>,
Kate Stewart <kstewart@...uxfoundation.org>,
Philippe Ombredanne <pombredanne@...b.com>
Subject: Re: [PATCH][RFC] module: Cure the MODULE_LICENSE "GPL" vs. "GPL v2"
bogosity
On Tue, 29 Jan 2019 15:11:40 +0100 (CET)
Thomas Gleixner <tglx@...utronix.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
Powered by blists - more mailing lists