From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Zhihang Shao <zhihang.shao.iscas@gmail.com>,
Andy Polyakov <appro@cryptogams.org>
Subject: Re: [PATCH v2 0/3] Consolidate Poly1305 code and add RISC-V optimization
Date: Tue, 26 Aug 2025 20:16:46 -0600 [thread overview]
Message-ID: <20250827021646.GA62136@quark> (raw)
In-Reply-To: <20250824025736.148576-1-ebiggers@kernel.org>
On Sat, Aug 23, 2025 at 10:57:33PM -0400, Eric Biggers wrote:
> This series is targeting libcrypto-next. It can also be retrieved from:
>
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git poly1305-v2
>
> This series simplifies and optimizes the organization of the Poly1305
> code by consolidating it into a single module. This follows the example
> of SHA-1, SHA-256, SHA-512, CRC32, etc.
>
> Since the RISC-V Poly1305 patch has had a moving target, I also rebased
> it on top of this series and included it as patch 3.
>
> Changed in v2:
> - Added missing 'FORCE' to the make rules for mips/poly1305-core.S
> and riscv/poly1305-core.S
>
> Eric Biggers (2):
> lib/crypto: poly1305: Remove unused function
> poly1305_is_arch_optimized()
> lib/crypto: poly1305: Consolidate into single module
>
> Zhihang Shao (1):
> lib/crypto: riscv/poly1305: Import OpenSSL/CRYPTOGAMS implementation
FYI, I applied this series to
https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=libcrypto-next
But as always, reviews and acks would be greatly appreciated!
- Eric
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-08-27 2:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 2:57 [PATCH v2 0/3] Consolidate Poly1305 code and add RISC-V optimization Eric Biggers
2025-08-24 2:57 ` [PATCH v2 1/3] lib/crypto: poly1305: Remove unused function poly1305_is_arch_optimized() Eric Biggers
2025-08-24 2:57 ` [PATCH v2 2/3] lib/crypto: poly1305: Consolidate into single module Eric Biggers
2025-08-29 4:11 ` Eric Biggers
2025-08-24 2:57 ` [PATCH v2 3/3] lib/crypto: riscv/poly1305: Import OpenSSL/CRYPTOGAMS implementation Eric Biggers
2025-08-27 2:16 ` Eric Biggers [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=20250827021646.GA62136@quark \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=appro@cryptogams.org \
--cc=ardb@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=zhihang.shao.iscas@gmail.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 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).