public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Kate Stewart <kstewart@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [patch 4/9] LICENSES/GPL2.0: Add GPL-2.0-only/or-later as valid identifiers
Date: Mon, 23 Apr 2018 07:14:53 -0300	[thread overview]
Message-ID: <20180423071453.25deeb48@vento.lan> (raw)
In-Reply-To: <20180423065229.GD4208@kroah.com>

Em Mon, 23 Apr 2018 08:52:29 +0200
Greg Kroah-Hartman <gregkh@linuxfoundation.org> escreveu:

> On Mon, Apr 23, 2018 at 12:02:12AM +0200, Thomas Gleixner wrote:
> > Quite some files have been flagged with the new GPL-2.0-only and
> > GPL-2.0-or-later identifiers which replace the original GPL-2.0 and
> > GPL-2.0+ identifiers in the SPDX license identifier specification, but the
> > identifiers are not mentioned as valid in the GPL-2.0 license file.
> > 
> > Add them to make everything consistent again.
> > 
> > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> > Cc: Hans Verkuil <hans.verkuil@cisco.com>
> > Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>  
> 
> As much as I dislike the "new" identifiers, I guess trying to hold them
> back is a pointless exercise :(

Well, it is part of the SPDX spec, so it should be valid, no matter
of personal tastes.

I'd say that we should clearly point what SPDX version is preferred at:
	Documentation/process/license-rules.rst

And, if we adopt version 3.0, change the described license tags
accordingly, as the tags showed there are for some pre-version 3.0
SPDX version (but the file doesn't mention if it follows SPDX version
1.0, 1.1, 1.2, 2.0 or 2.1).

Anyway, for this specific patch:

Reviewed-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>


Thanks,
Mauro

  parent reply	other threads:[~2018-04-23 10:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-22 22:02 [patch 0/9] LICENSES: Add missing License Text and fixup bogus identifiers Thomas Gleixner
2018-04-22 22:02 ` [patch 1/9] x86/jailhouse: Fix incorrect SPDX identifier Thomas Gleixner
2018-04-23  6:52   ` Jan Kiszka
2018-04-23  8:22   ` [tip:x86/urgent] " tip-bot for Thomas Gleixner
2018-04-22 22:02 ` [patch 2/9] pinctrl: sh-pfc: r8a77965: Fixup " Thomas Gleixner
2018-04-23  9:17   ` Geert Uytterhoeven
2018-04-22 22:02 ` [patch 3/9] ARM: S3C24XX: Fix invalid " Thomas Gleixner
2018-04-23 15:26   ` Krzysztof Kozlowski
2018-04-24 13:27   ` Christoph Hellwig
2018-04-22 22:02 ` [patch 4/9] LICENSES/GPL2.0: Add GPL-2.0-only/or-later as valid identifiers Thomas Gleixner
2018-04-23  6:52   ` Greg Kroah-Hartman
2018-04-23  7:19     ` Hans Verkuil
2018-04-23 10:14     ` Mauro Carvalho Chehab [this message]
2018-04-24  8:01       ` Thomas Gleixner
2018-04-23 18:24   ` Kate Stewart
2018-04-22 22:02 ` [patch 5/9] LICENSES: Add X11 license Thomas Gleixner
2018-04-23  6:50   ` Greg Kroah-Hartman
2018-04-22 22:02 ` [patch 6/9] LICENSES: Add CDDL-1.0 license text Thomas Gleixner
2018-04-23  6:51   ` Greg Kroah-Hartman
2018-04-22 22:02 ` [patch 7/9] LICENSES: Add Apache 2.0 " Thomas Gleixner
2018-04-23  6:51   ` Greg Kroah-Hartman
2018-04-22 22:02 ` [patch 8/9] LICENSES: Add CC-BY-SA-4.0 " Thomas Gleixner
2018-04-23  6:54   ` Greg Kroah-Hartman
2018-04-23  7:37     ` Thomas Gleixner
2018-04-23  8:26       ` Greg Kroah-Hartman
2018-04-23 10:21         ` Mauro Carvalho Chehab
2018-04-23 12:29         ` Jonathan Corbet
2018-04-22 22:02 ` [patch 9/9] LICENSES: Add Linux-OpenIB " Thomas Gleixner
2018-04-23  6:55   ` Greg Kroah-Hartman
2018-04-23  6:57 ` [patch 0/9] LICENSES: Add missing License Text and fixup bogus identifiers Greg Kroah-Hartman
2018-04-23  7:34   ` Thomas Gleixner

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=20180423071453.25deeb48@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hans.verkuil@cisco.com \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pombredanne@nexb.com \
    --cc=tglx@linutronix.de \
    /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