From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Biggers <ebiggers@kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Ard Biesheuvel <ardb@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto List <linux-crypto@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the libcrypto tree
Date: Mon, 20 Oct 2025 10:39:15 +1100 [thread overview]
Message-ID: <20251020103915.6f203f67@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
Hi all,
The following commits are also in the crypto tree as different commits
(but the same patches):
3bb8775a518f ("crypto: x86/aes-gcm - optimize long AAD processing with AVX512")
5a530ed1e321 ("crypto: x86/aes-gcm - optimize AVX512 precomputation of H^2 from H^1")
e274d2ebb428 ("crypto: x86/aes-gcm - revise some comments in AVX512 code")
08080b1ea549 ("crypto: x86/aes-gcm - reorder AVX512 precompute and aad_update functions")
42d929de14fb ("crypto: x86/aes-gcm - clean up AVX512 code to assume 512-bit vectors")
9bc4bcca89e4 ("crypto: x86/aes-gcm - rename avx10 and avx10_512 to avx512")
d03a8a0dc347 ("crypto: x86/aes-gcm - remove VAES+AVX10/256 optimized code")
These are commits
a7098b73a98c ("crypto: x86/aes-gcm - optimize long AAD processing with AVX512")
decb160d8a39 ("crypto: x86/aes-gcm - optimize AVX512 precomputation of H^2 from H^1")
4d1fe69597a6 ("crypto: x86/aes-gcm - revise some comments in AVX512 code")
12249403d1ef ("crypto: x86/aes-gcm - reorder AVX512 precompute and aad_update functions")
99713223854d ("crypto: x86/aes-gcm - clean up AVX512 code to assume 512-bit vectors")
d4acd8519d2a ("crypto: x86/aes-gcm - rename avx10 and avx10_512 to avx512")
bbe0e2274a45 ("crypto: x86/aes-gcm - remove VAES+AVX10/256 optimized code")
in the crypto tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2025-10-19 23:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251020103915.6f203f67@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®