From: Christoph Hellwig <hch@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Krzysztof Kozlowski <krzk@kernel.org>,
Arnaud Patard <arnaud.patard@rtp-net.org>,
Ben Dooks <ben-linux@fluff.org>,
Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: [patch 3/9] ARM: S3C24XX: Fix invalid SPDX identifier
Date: Tue, 24 Apr 2018 06:27:59 -0700 [thread overview]
Message-ID: <20180424132759.GA31133@infradead.org> (raw)
In-Reply-To: <20180422220832.982315239@linutronix.de>
On Mon, Apr 23, 2018 at 12:02:11AM +0200, Thomas Gleixner wrote:
> GPL-1.0 is not part of the valid identifier list and as its meaning is GPL
> version 1.0 only this would be incompatible with the kernel license.
>
> As this code was included into the kernel, assume its GPL-1.0+
>
> Fixes: 84b2170109e4 ("ARM: S3C24XX: Add SPDX license identifiers")
Before that commit the file just said GNU General Public License and
referred to the COPYING file. Which to me suggests it is at best
GPL-2.0+ if not GPL-2.0.
Hopefully the original author can still be reached to clear this up.
next prev parent reply other threads:[~2018-04-24 13:27 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 [this message]
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
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=20180424132759.GA31133@infradead.org \
--to=hch@infradead.org \
--cc=arnaud.patard@rtp-net.org \
--cc=ben-linux@fluff.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=rmk+kernel@arm.linux.org.uk \
--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