LKML Archive on
help / color / mirror / Atom feed
From: J Lovejoy <>
To: Alexios Zavras <>
Cc: Alexandre Belloni <>,
	Greg KH <>,
	Linus Torvalds <>,
	Andrew Morton <>,
	Thomas Gleixner <>,
	"" <>,
	"" <>
Subject: Re: [GIT PULL] SPDX update for 5.2-rc1 - round 1
Date: Thu, 30 May 2019 18:25:18 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

HI all,

Sorry I didn’t jump in here sooner. Just a bit of additional background info to what Thomas and Alexios have already provided below:

> On May 29, 2019, at 8:16 AM, Zavras, Alexios <> wrote:
>> -----Original Message-----
>> From: <>
>> On Behalf Of Alexandre Belloni
>> Sent: Wednesday, 29 May, 2019 15:13
>> Subject: Re: [GIT PULL] SPDX update for 5.2-rc1 - round 1
>> Hello,
>> On 21/05/2019 15:32:57+0200, Greg KH wrote:
>>>  - Add GPL-2.0-only or GPL-2.0-or-later tags to files where our scan
>> I'm very confused by those two tags because they are not mentioned in the
>> SPDX 2.1 specification or the kernel documentation and seem to just be from
>> which doesn't seem to be versionned anywhere.
>> While I understand the rationale behind those, I believe the correct way of
>> introducing them would be first to add them in the spec and documentation
>> and then make use of them.
> The "GPL-2.0-only" and "GPL-2.0-or-later" are license short identifiers.
> They do not belong to the SPDX spec, but rather on the license list.
> They were introduced in the SPDX License List v3.0 (current version is 3.5):
> It seems the examples in the kernel documentation use identifiers
> from earlier versions of the license list.

As Thomas mentioned in another part of this thread, the identifiers for the GNU family of licenses was changed as of v3.0 of the SPDX License List in Dec 2017. See for a explanation and for the impetus of the change. (Note, the SPDX License List has its own versioning separate from the SPDX Spec.)  We don’t change the license identifiers lightly and have only done so for very specific and limited reasons, so you can be sure there was a LOT of discussion over this change. Unfortunately, the lengthy discussion happened to coincide with the beginning of the work here on using the SPDX identifiers in the kernel. In a perfect world, we would have completed that change before you all started this, but sometimes things don’t go according to best timing!

>> Now, what should we do with all the GPL-2.0 and GPL-2.0+ tags that we have?
> These are still valid identifiers (albeit deprecated), 
> so there is no urgent need to have them replaced.

This is correct. It would be nice if any new identifiers used the current ones. If the old identifiers get updated as other patches are done to those files or something organic like that, that would be great, but no rush. We’ve got plenty to focus on with getting the identifiers in there, sorting out the “messy” files and so on!

Thanks again for all the work on this!

SPDX legal team co-lead

> -- zvr -
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0,
> Managing Directors: Christin Eisenschmid, Gary Kershaw
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928

      parent reply	other threads:[~2019-05-31  0:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 13:32 Greg KH
2019-05-21 19:55 ` pr-tracker-bot
2019-05-21 19:56 ` Linus Torvalds
2019-05-22 16:34   ` Greg KH
2019-05-22  4:32 ` Masahiro Yamada
2019-05-22  6:34   ` Joe Perches
2019-05-22 10:14     ` Thomas Gleixner
2019-05-23  2:49     ` Masahiro Yamada
2019-05-23  2:57       ` Joe Perches
2019-05-23  5:33         ` Thomas Gleixner
2019-06-25 11:19     ` Masahiro Yamada
2019-05-29 13:13 ` Alexandre Belloni
2019-05-29 13:51   ` Thomas Gleixner
2019-05-29 14:16   ` Zavras, Alexios
     [not found]     ` <>
2019-05-31  0:25       ` J Lovejoy [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [GIT PULL] SPDX update for 5.2-rc1 - round 1' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).