From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [patch 0/9] LICENSES: Add missing License Text and fixup bogus identifiers
Date: Mon, 23 Apr 2018 08:57:00 +0200 [thread overview]
Message-ID: <20180423065700.GG4208@kroah.com> (raw)
In-Reply-To: <20180422220208.772527041@linutronix.de>
On Mon, Apr 23, 2018 at 12:02:08AM +0200, Thomas Gleixner wrote:
> There are a few bogus SPDX identifiers in various files and SPDX
> Identifiers used in tree or about to be used which have no corresponding
> License Text file in the LICENSES directory or use the new variant of the
> GPL-2.0[+] license identifiers which are not mentioned in the GPL-2.0
> Valid-License-Identifiers: tags.
>
> The following series cleans that up:
>
> - Use the proper identifiers
>
> - Add GPL-2.0-only and GPL-2.0-or-later identifiers to the GPL2.0 license
>
> - Add X11, Apache-2.0, CC-BY-SA-4.0, CCDL-1.0, Linux-OpenIB license texts
> to the LICENSES directory along with the required documentation texts
I'm thinking we need a script to keep these in check, right? Does
checkpatch.pl handle knowing what the "currently good" list of license
tags are, or should we just use a separate script to parse the LICENSES/
directory to get that list?
Either way, nice work on this series, thanks for keeping up with them.
thanks,
greg k-h
next prev parent reply other threads:[~2018-04-23 6:57 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
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 ` Greg Kroah-Hartman [this message]
2018-04-23 7:34 ` [patch 0/9] LICENSES: Add missing License Text and fixup bogus identifiers 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=20180423065700.GG4208@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--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 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.