From: Kees Cook <keescook@chromium.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: tglx@linutronix.de, gregkh@linuxfoundation.org,
akpm@linux-foundation.org, shuah@kernel.org, joe@perches.com,
rostedt@goodmis.org, linux-spdx@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Goldwyn Rodrigues <rgoldwyn@suse.com>, Kuno Woudt <kuno@frob.nl>,
Richard Fontana <fontana@sharpeleven.org>,
copyleft-next@lists.fedorahosted.org,
Ciaran Farrell <Ciaran.Farrell@suse.com>,
Christopher De Nicolo <Christopher.DeNicolo@suse.com>,
Christoph Hellwig <hch@lst.de>, Jonathan Corbet <corbet@lwn.net>,
Thorsten Leemhuis <linux@leemhuis.info>
Subject: Re: [PATCH v10 1/2] LICENSES: Add the copyleft-next-0.3.1 license
Date: Sat, 1 Oct 2022 08:08:12 -0700 [thread overview]
Message-ID: <202210010804.206AED744@keescook> (raw)
In-Reply-To: <20220914060147.1934064-2-mcgrof@kernel.org>
On Tue, Sep 13, 2022 at 11:01:46PM -0700, Luis Chamberlain wrote:
> Add the full text of the copyleft-next-0.3.1 license to the kernel
> tree as well as the required tags for reference and tooling.
> The license text was copied directly from the copyleft-next project's
> git tree [0].
>
> Discussion of using copyleft-next-0.3.1 on Linux started since June,
> 2016 [1]. In the end Linus' preference was to have drivers use
> MODULE_LICENSE("GPL") to make it clear that the GPL applies when it
> comes to Linux [2]. Additionally, even though copyleft-next-0.3.1 has
> been found to be to be GPLv2 compatible by three attorneys at SUSE and
> Redhat [3], to err on the side of caution we simply recommend to
> always use the "OR" language for this license [4].
IANA copyright lawyer, but the use of "OR" seems sensible to me, and I
see no reason to NOT add this license.
> [...]
> LICENSES/dual/copyleft-next-0.3.1 | 236 ++++++++++++++++++++++++++++++
> [...]
> +SPDX-URL: https://spdx.org/licenses/copyleft-next-0.3.1
The contents[1] of this license match the patch.
Reviewed-by: Kees Cook <keescook@chromium.org>
-Kees
[1] https://raw.githubusercontent.com/copyleft-next/copyleft-next/master/Releases/copyleft-next-0.3.1
--
Kees Cook
next prev parent reply other threads:[~2022-10-01 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 6:01 [PATCH v10 0/2] SPDX: add copyleft-next-0.3.1 Luis Chamberlain
2022-09-14 6:01 ` [PATCH v10 1/2] LICENSES: Add the copyleft-next-0.3.1 license Luis Chamberlain
2022-10-01 15:08 ` Kees Cook [this message]
2022-09-14 6:01 ` [PATCH v10 2/2] testing: use the copyleft-next-0.3.1 SPDX tag Luis Chamberlain
2022-10-01 14:58 ` Kees Cook
2022-09-30 20:06 ` [PATCH v10 0/2] SPDX: add copyleft-next-0.3.1 Luis Chamberlain
2022-10-01 7:09 ` Greg KH
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=202210010804.206AED744@keescook \
--to=keescook@chromium.org \
--cc=Christopher.DeNicolo@suse.com \
--cc=Ciaran.Farrell@suse.com \
--cc=akpm@linux-foundation.org \
--cc=copyleft-next@lists.fedorahosted.org \
--cc=corbet@lwn.net \
--cc=fontana@sharpeleven.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=joe@perches.com \
--cc=kuno@frob.nl \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mcgrof@kernel.org \
--cc=rgoldwyn@suse.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).