From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linuxfoundation.org>,
Andrew Morton <akpm@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Kate Stewart <kstewart@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@lst.de>,
Russell King <rmk+kernel@armlinux.org.uk>,
Rob Herring <rob.herring@linaro.org>,
Jonas Oberg <jonas@fsfe.org>, Joe Perches <joe@perches.com>,
linux-xfs@vger.kernel.org,
Charlemagne Lasse <charlemagnelasse@gmail.com>,
Carmen Bianca Bakker <carmenbianca@fsfe.org>
Subject: Re: [patch V4 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses
Date: Tue, 5 Dec 2017 07:50:03 +0100 [thread overview]
Message-ID: <20171205065003.GB7782@osiris> (raw)
In-Reply-To: <20171204212120.484179273@linutronix.de>
On Mon, Dec 04, 2017 at 10:19:28PM +0100, Thomas Gleixner wrote:
> +3. Syntax:
> +
> + A <SPDX License Expression> is either an SPDX short form license
> + identifier found on the SPDX License List, or when multiple licenses
> + apply, an expression consisting of keywords "AND", "OR", and "WITH"
> + separating SPDX short form license identifiers surrounded by "(", ")".
Here it is stated that SPDX identifiers using the keyword WITH must be
surrounded by braces.
> + // SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note)
> + // SPDX-License-Identifier: (GPL-2.0+ WITH Linux-syscall-note)
Just like this example.
> + File format examples::
> +
> + SPDX-Exception-Identifier: Linux-syscall-note
> + SPDX-URL: https://spdx.org/licenses/Linux-syscall-note.html
> + SPDX-Licenses: GPL-2.0, GPL-2.0+, GPL-1.0+, LGPL-2.0, LGPL-2.0+, LGPL-2.1, LGPL-2.1+
> + Usage-Guidance:
> + This exception is used together with one of the above SPDX-Licenses
> + to mark user-space API (uapi) header files so they can be included
> + into non GPL compliant user-space application code.
> + To use this exception add it with the keyword WITH to one of the
> + identifiers in the SPDX-Licenses tag:
> + SPDX-License-Identifier: <SPDX-License> WITH Linux-syscall-note
But here it comes without braces.
> + Exception-Text:
> + Full exception text
> +
> + ::
> +
> + SPDX-Exception-Identifier: GCC-exception-2.0
> + SPDX-URL: https://spdx.org/licenses/GCC-exception-2.0.html
> + SPDX-Licenses: GPL-2.0, GPL-2.0+
> + Usage-Guidance:
> + The "GCC Runtime Library exception 2.0" is used together with one
> + of the above SPDX-Licenses for code imported from the GCC runtime
> + library.
> + To use this exception add it with the keyword WITH to one of the
> + identifiers in the SPDX-Licenses tag:
> + SPDX-License-Identifier: <SPDX-License> WITH GCC-exception-2.0
Here as well.
The whole kernel now got SPDX-License-Identifiers that look like this:
SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note
So this looks inconsistent to me, or did I miss something?
next prev parent reply other threads:[~2017-12-05 6:50 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 21:19 [patch V4 00/11] LICENSES: Add documentation and initial License files Thomas Gleixner
2017-12-04 21:19 ` [patch V4 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses Thomas Gleixner
2017-12-05 6:50 ` Heiko Carstens [this message]
2017-12-08 15:29 ` Philippe Ombredanne
2017-12-09 11:03 ` Philippe Ombredanne
2017-12-11 21:58 ` Jonathan Corbet
2017-12-04 21:19 ` [patch V4 02/11] LICENSES: Add the GPL 2.0 license Thomas Gleixner
2017-12-05 7:36 ` Greg Kroah-Hartman
2017-12-06 21:00 ` Philippe Ombredanne
2017-12-07 10:51 ` Jonas Oberg
2017-12-08 3:40 ` Darrick J. Wong
2017-12-04 21:19 ` [patch V4 03/11] LICENSES: Add the LGPL " Thomas Gleixner
2017-12-04 21:19 ` [patch V4 04/11] LICENSES: Add the LGPL-2.1 license Thomas Gleixner
2017-12-04 21:19 ` [patch V4 05/11] LICENSES: Add the BSD 2-clause "Simplified" license Thomas Gleixner
2017-12-04 21:19 ` [patch V4 06/11] LICENSES: Add the BSD 3-clause "New" or "Revised" License Thomas Gleixner
2017-12-04 21:19 ` [patch V4 07/11] LICENSES: Add the BSD-3-clause "Clear" license Thomas Gleixner
2017-12-04 21:19 ` [patch V4 08/11] LICENSES: Add the MIT license Thomas Gleixner
2017-12-04 21:19 ` [patch V4 09/11] LICENSES: Add Linux syscall note exception Thomas Gleixner
2017-12-04 21:19 ` [patch V4 10/11] LICENSES: Add the GPL 1.0 license Thomas Gleixner
2017-12-04 21:19 ` [patch V4 11/11] LICENSES: Add MPL-1.1 license Thomas Gleixner
2017-12-09 11:09 ` [patch V4 00/11] LICENSES: Add documentation and initial License files Philippe Ombredanne
-- strict thread matches above, loose matches on Subject: below --
2017-11-16 18:33 [patch V2 " Thomas Gleixner
2017-11-16 18:33 ` [patch V2 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses Thomas Gleixner
2017-11-17 10:00 ` [patch V4 " Thomas Gleixner
2017-11-17 11:58 ` Philippe Ombredanne
[not found] ` <CAG_66ZRPXxodLw=eeTRtXuRGfvmonVNknzNmMuNMVooJgd1Uxw@mail.gmail.com>
2017-11-17 13:16 ` Thomas Gleixner
2017-11-17 17:06 ` Mauro Carvalho Chehab
2017-11-17 18:11 ` Thomas Gleixner
2017-11-17 18:39 ` Christoph Hellwig
2017-11-22 11:12 ` Thomas Gleixner
2017-11-22 11:51 ` Mauro Carvalho Chehab
2017-11-22 13:23 ` Christoph Hellwig
2017-11-22 13:35 ` Mauro Carvalho Chehab
2017-11-22 13:48 ` Greg Kroah-Hartman
2017-11-25 19:04 ` Pavel Machek
2017-11-25 19:11 ` Linus Torvalds
2017-11-25 19:17 ` Pavel Machek
2017-11-25 19:30 ` Linus Torvalds
2017-11-25 19:53 ` Mauro Carvalho Chehab
2017-11-25 20:30 ` Linus Torvalds
2017-11-25 18:51 ` Pavel Machek
2017-11-25 23:41 ` Philippe Ombredanne
2017-11-17 19:02 ` Jonas Oberg
2017-12-14 16:25 ` Joe Perches
2017-12-14 16:29 ` 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=20171205065003.GB7782@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linuxfoundation.org \
--cc=carmenbianca@fsfe.org \
--cc=charlemagnelasse@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=joe@perches.com \
--cc=jonas@fsfe.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rob.herring@linaro.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linuxfoundation.org \
/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;
as well as URLs for NNTP newsgroup(s).