From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 3/3] LICENSES: add Linux-syscall-note exception text
Date: Fri, 8 May 2020 08:21:49 +0200 [thread overview]
Message-ID: <20200508062149.30753-3-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20200508062149.30753-1-a.fatoum@pengutronix.de>
We include Linux headers in barebox, which are licensed under GPL with
this exception.
While we are GPL-2.0 as well and don't require the exception, we should
always provide license texts to the License-Identifiers we are using.
At the time of this writing these are:
* BSD-1-Clause
* BSD-2-Clause
* BSD-3-Clause
* GPL-2.0-only, -or-later and WITH Linux-syscall-note
* LGPL-2.1 and -or-later
* MIT
* X11
* ISC
With this commit, our LICENSES directory now contains licenses for all
of them.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
LICENSES/exceptions/Linux-syscall-note | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
create mode 100644 LICENSES/exceptions/Linux-syscall-note
diff --git a/LICENSES/exceptions/Linux-syscall-note b/LICENSES/exceptions/Linux-syscall-note
new file mode 100644
index 000000000000..9abdad71fafd
--- /dev/null
+++ b/LICENSES/exceptions/Linux-syscall-note
@@ -0,0 +1,25 @@
+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+, GPL-2.0-only, GPL-2.0-or-later
+Usage-Guide:
+ 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
+License-Text:
+
+ NOTE! This copyright does *not* cover user programs that use kernel
+ services by normal system calls - this is merely considered normal use
+ of the kernel, and does *not* fall under the heading of "derived work".
+ Also note that the GPL below is copyrighted by the Free Software
+ Foundation, but the instance of code that it refers to (the Linux
+ kernel) is copyrighted by me and others who actually wrote it.
+
+ Also note that the only valid version of the GPL as far as the kernel
+ is concerned is _this_ particular version of the license (ie v2, not
+ v2.2 or v3.x or whatever), unless explicitly otherwise stated.
+
+ Linus Torvalds
+
--
2.26.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-05-08 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 6:21 [PATCH 1/3] LICENSES: replace LGPL-2.1-or-later with Linux license text Ahmad Fatoum
2020-05-08 6:21 ` [PATCH 2/3] LICENSES: import ISC/X11/BSD-2-Clause license Text from Linux Ahmad Fatoum
2020-05-10 16:20 ` Roland Hieber
2020-05-08 6:21 ` Ahmad Fatoum [this message]
2020-05-10 16:22 ` [PATCH 3/3] LICENSES: add Linux-syscall-note exception text Roland Hieber
2020-05-10 16:14 ` [PATCH 1/3] LICENSES: replace LGPL-2.1-or-later with Linux license text Roland Hieber
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=20200508062149.30753-3-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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