All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH 0/3] crypto - some SPDX cleanups for arch code
Date: Fri, 9 Jun 2023 20:12:48 -0700	[thread overview]
Message-ID: <20230610031248.GC872@sol.localdomain> (raw)
In-Reply-To: <20230607043730.GB941@sol.localdomain>

On Tue, Jun 06, 2023 at 09:37:30PM -0700, Eric Biggers wrote:
> On Tue, Jun 06, 2023 at 07:31:24PM +0200, Ard Biesheuvel wrote:
> > Some SPDX cleanups for the arch crypto code on ARM, arm64 and x86
> > 
> > Ard Biesheuvel (3):
> >   crypto: arm64 - add some missing SPDX headers
> >   crypto: arm - add some missing SPDX headers
> >   crypto: x86 - add some missing SPDX headers
> > 
> >  arch/arm/crypto/chacha-neon-core.S          | 10 +----
> >  arch/arm/crypto/crc32-ce-core.S             | 30 ++-----------
> >  arch/arm/crypto/crct10dif-ce-core.S         | 40 +----------------
> >  arch/arm64/crypto/chacha-neon-core.S        | 10 +----
> >  arch/arm64/crypto/chacha-neon-glue.c        | 10 +----
> >  arch/arm64/crypto/crct10dif-ce-core.S       | 40 +----------------
> >  arch/x86/crypto/aesni-intel_avx-x86_64.S    | 36 +--------------
> >  arch/x86/crypto/camellia-aesni-avx-asm_64.S |  7 +--
> >  arch/x86/crypto/crc32-pclmul_glue.c         | 24 +---------
> >  arch/x86/crypto/crc32c-pcl-intel-asm_64.S   | 29 +-----------
> >  arch/x86/crypto/crct10dif-pcl-asm_64.S      | 36 +--------------
> >  arch/x86/crypto/crct10dif-pclmul_glue.c     | 16 +------
> >  arch/x86/crypto/sha1_avx2_x86_64_asm.S      | 46 +-------------------
> >  arch/x86/crypto/sha1_ni_asm.S               | 46 +-------------------
> >  arch/x86/crypto/sha256-avx-asm.S            | 28 +-----------
> >  arch/x86/crypto/sha256-avx2-asm.S           | 29 +-----------
> >  arch/x86/crypto/sha256-ssse3-asm.S          | 29 +-----------
> >  arch/x86/crypto/sha256_ni_asm.S             | 46 +-------------------
> >  arch/x86/crypto/sha256_ssse3_glue.c         | 15 +------
> >  arch/x86/crypto/sha512-avx-asm.S            | 29 +-----------
> >  arch/x86/crypto/sha512-avx2-asm.S           | 29 +-----------
> >  arch/x86/crypto/sha512-ssse3-asm.S          | 29 +-----------
> >  arch/x86/crypto/sha512_ssse3_glue.c         | 16 +------
> >  arch/x86/crypto/twofish_glue.c              | 16 +------
> >  24 files changed, 26 insertions(+), 620 deletions(-)
> 
> Reviewed-by: Eric Biggers <ebiggers@google.com>
> 

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.

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.

* Replacing with SPDX on files that explicitly say "DO NOT ALTER OR REMOVE
  COPYRIGHT NOTICES OR THIS FILE HEADER."

* 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)

* 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.

- Eric

  reply	other threads:[~2023-06-10  3:12 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 [this message]
2023-06-10  7:25     ` Bagas Sanjaya

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=20230610031248.GC872@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=ardb@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.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 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.