From: Eric Biggers <ebiggers@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Jason@zx2c4.com, Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, sparclinux@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH v2 5/9] lib/crypto: riscv: move arch/riscv/lib/crypto/ into lib/crypto/
Date: Mon, 23 Jun 2025 19:44:51 -0700 [thread overview]
Message-ID: <20250624024451.GA7127@sol> (raw)
In-Reply-To: <mhng-8FC37478-859D-40EA-A0E9-3EA86429DC53@palmerdabbelt-mac>
On Mon, Jun 23, 2025 at 04:23:52PM -0700, Palmer Dabbelt wrote:
> On Thu, 19 Jun 2025 12:19:04 PDT (-0700), ebiggers@kernel.org wrote:
> > From: Eric Biggers <ebiggers@google.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@google.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@dabbelt.com>
>
Yes, I'm taking this series through libcrypto-next. Thanks!
- Eric
next prev parent reply other threads:[~2025-06-24 2:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 19:18 [PATCH v2 0/9] lib/crypto: move arch/$(ARCH)/lib/crypto/ to lib/crypto/$(ARCH)/ Eric Biggers
2025-06-19 19:19 ` [PATCH v2 1/9] lib/crypto: arm: move arch/arm/lib/crypto/ into lib/crypto/ Eric Biggers
2025-06-19 19:19 ` [PATCH v2 2/9] lib/crypto: arm64: move arch/arm64/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` [PATCH v2 3/9] lib/crypto: mips: move arch/mips/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` [PATCH v2 4/9] lib/crypto: powerpc: move arch/powerpc/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` [PATCH v2 5/9] lib/crypto: riscv: move arch/riscv/lib/crypto/ " Eric Biggers
2025-06-23 23:23 ` Palmer Dabbelt
2025-06-24 2:44 ` Eric Biggers [this message]
2025-06-19 19:19 ` [PATCH v2 6/9] lib/crypto: s390: move arch/s390/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` [PATCH v2 7/9] lib/crypto: sparc: move arch/sparc/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` [PATCH v2 8/9] lib/crypto: x86: move arch/x86/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` [PATCH v2 9/9] MAINTAINERS: drop arch/*/lib/crypto/ pattern Eric Biggers
2025-06-20 21:29 ` [PATCH v2 0/9] lib/crypto: move arch/$(ARCH)/lib/crypto/ to lib/crypto/$(ARCH)/ Eric Biggers
2025-06-20 21:39 ` Ard Biesheuvel
2025-06-20 22:41 ` Sohil Mehta
2025-06-21 2:53 ` Martin K. Petersen
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=20250624024451.GA7127@sol \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=palmer@dabbelt.com \
--cc=sparclinux@vger.kernel.org \
--cc=x86@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 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).