From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Eric Biggers <ebiggers@kernel.org>, Ard Biesheuvel <ardb@kernel.org>
Cc: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
Richard Fontana <rfontana@redhat.com>
Subject: Re: [PATCH 0/3] crypto - some SPDX cleanups for arch code
Date: Sat, 10 Jun 2023 14:25:37 +0700 [thread overview]
Message-ID: <ZIQlcc_9lyWtP0Jg@debian.me> (raw)
In-Reply-To: <20230610031248.GC872@sol.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2071 bytes --]
On Fri, Jun 09, 2023 at 08:12:48PM -0700, Eric Biggers wrote:
> Actually, given the discussion on the other thread
> https://lore.kernel.org/r/20230607053940.39078-10-bagasdotme@gmail.com, maybe it
> would be best to hold off on this for now? Or at least split this series into
> more patches, such that each patch does only one "type" of SPDX replacement.
Thanks for pointing to my thread! (and Cc'ing Richard of course ...)
If we continue on the conversion, I definitely agree with your latter
option (as I have done there).
>
> I still think these conversions are probably fine, but some points that perhaps
> need an explicit explanation are:
>
> * Using GPL-2.0-only for files like chacha-neon-core.S whose file header says
> GPL v2, but also says GPL v2 or later.
In that case, IMO, err to the safe side and assume the most restrictive
(GPL-2.0-only).
>
> * Replacing with SPDX on files that explicitly say "DO NOT ALTER OR REMOVE
> COPYRIGHT NOTICES OR THIS FILE HEADER."
Just add the SPDX tag...
>
> * Using BSD-3-Clause when the license text in the file header has the copyright
> holder name instead of "copyright holder", thus making it not an exact
> word-for-word match with LICENSES/preferred/BSD-3-Clause. (It seems there are
> specific rules for variations that have been approved, e.g. see
> https://github.com/spdx/license-list-XML/blob/main/src/BSD-3-Clause.xml and
> https://spdx.github.io/spdx-spec/v2.2.2/license-matching-guidelines-and-templates)
Above case is wording variation (for which we conclude that only license
boilerplate with exact wording can be replaced by the tag).
>
> * Using "GPL-2.0-only OR BSD-3-Clause" for the two crct10dif-ce-core.S files.
> They have an unusual file header, and it could be argued that some
> contributions to those files were intended to be licensed under GPL-2.0-only.
> FWIW, I am fine with either license for my contributions to those files.
Dunno.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-06-10 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 17:31 [PATCH 0/3] crypto - some SPDX cleanups for arch code Ard Biesheuvel
2023-06-06 17:31 ` [PATCH 1/3] crypto: arm64 - add some missing SPDX headers Ard Biesheuvel
2023-06-06 17:31 ` [PATCH 2/3] crypto: arm " Ard Biesheuvel
2023-06-10 7:30 ` Bagas Sanjaya
2023-06-20 3:50 ` Richard Fontana
2023-06-23 18:37 ` Ard Biesheuvel
2023-06-06 17:31 ` [PATCH 3/3] crypto: x86 " Ard Biesheuvel
2023-06-07 4:37 ` [PATCH 0/3] crypto - some SPDX cleanups for arch code Eric Biggers
2023-06-10 3:12 ` Eric Biggers
2023-06-10 7:25 ` Bagas Sanjaya [this message]
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=ZIQlcc_9lyWtP0Jg@debian.me \
--to=bagasdotme@gmail.com \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=rfontana@redhat.com \
/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.