[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250624024451.GA7127@sol>
Date: Mon, 23 Jun 2025 19:44:51 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: Palmer Dabbelt <palmer@...belt.com>
Cc: linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
Jason@...c4.com, Ard Biesheuvel <ardb@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-mips@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-riscv@...ts.infradead.org,
linux-s390@...r.kernel.org, sparclinux@...r.kernel.org,
x86@...nel.org
Subject: Re: [PATCH v2 5/9] lib/crypto: riscv: move arch/riscv/lib/crypto/
into lib/crypto/
On Mon, Jun 23, 2025 at 04:23:52PM -0700, Palmer Dabbelt wrote:
> On Thu, 19 Jun 2025 12:19:04 PDT (-0700), ebiggers@...nel.org wrote:
> > From: Eric Biggers <ebiggers@...gle.com>
> >
> > Move the contents of arch/riscv/lib/crypto/ into lib/crypto/riscv/.
> >
> > The new code organization makes a lot more sense for how this code
> > actually works and is developed. In particular, it makes it possible to
> > build each algorithm as a single module, with better inlining and dead
> > code elimination. For a more detailed explanation, see the patchset
> > which did this for the CRC library code:
> > https://lore.kernel.org/r/20250607200454.73587-1-ebiggers@kernel.org/.
> > Also see the patchset which did this for SHA-512:
> > https://lore.kernel.org/linux-crypto/20250616014019.415791-1-ebiggers@kernel.org/
> >
> > This is just a preparatory commit, which does the move to get the files
> > into their new location but keeps them building the same way as before.
> > Later commits will make the actual improvements to the way the
> > arch-optimized code is integrated for each algorithm.
> >
> > Signed-off-by: Eric Biggers <ebiggers@...gle.com>
> > ---
> > arch/riscv/lib/Makefile | 1 -
> > lib/crypto/Kconfig | 2 +-
> > lib/crypto/Makefile | 1 +
> > {arch/riscv/lib/crypto => lib/crypto/riscv}/Kconfig | 0
> > {arch/riscv/lib/crypto => lib/crypto/riscv}/Makefile | 0
> > .../riscv/lib/crypto => lib/crypto/riscv}/chacha-riscv64-glue.c | 0
> > .../riscv/lib/crypto => lib/crypto/riscv}/chacha-riscv64-zvkb.S | 0
> > .../crypto/riscv}/sha256-riscv64-zvknha_or_zvknhb-zvkb.S | 0
> > {arch/riscv/lib/crypto => lib/crypto/riscv}/sha256.c | 0
> > 9 files changed, 2 insertions(+), 2 deletions(-)
> > rename {arch/riscv/lib/crypto => lib/crypto/riscv}/Kconfig (100%)
> > rename {arch/riscv/lib/crypto => lib/crypto/riscv}/Makefile (100%)
> > rename {arch/riscv/lib/crypto => lib/crypto/riscv}/chacha-riscv64-glue.c (100%)
> > rename {arch/riscv/lib/crypto => lib/crypto/riscv}/chacha-riscv64-zvkb.S (100%)
> > rename {arch/riscv/lib/crypto => lib/crypto/riscv}/sha256-riscv64-zvknha_or_zvknhb-zvkb.S (100%)
> > rename {arch/riscv/lib/crypto => lib/crypto/riscv}/sha256.c (100%)
>
> I'm assuming you want to keep these all together.
>
> Acked-by: Palmer Dabbelt <palmer@...belt.com>
>
Yes, I'm taking this series through libcrypto-next. Thanks!
- Eric
Powered by blists - more mailing lists