From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, "Ard Biesheuvel" <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
x86@kernel.org, "Borislav Petkov" <bp@alien8.de>,
"Carlos López" <clopez@suse.de>,
"Alexey Kardashevskiy" <aik@amd.com>
Subject: Re: [PATCH 0/3] Remove old AES-GCM library
Date: Wed, 29 Jul 2026 18:37:08 -0700 [thread overview]
Message-ID: <20260730013708.GA91995@quark> (raw)
In-Reply-To: <20260722025338.33354-1-ebiggers@kernel.org>
On Tue, Jul 21, 2026 at 07:53:35PM -0700, Eric Biggers wrote:
> The old AES-GCM library code is being replaced as part of an overhaul
> that is adding support for all the common AES encryption modes with
> consistent conventions
> (https://lore.kernel.org/linux-crypto/20260715221153.246410-1-ebiggers@kernel.org/).
>
> The SEV code is the only user of the old API. Update it to use the new
> API instead. Then remove the old API.
>
> This applies to libcrypto-next. If possible I'd like to take this
> through libcrypto-next for 7.3. Acks are appreciated.
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=libcrypto-next
- Eric
prev parent reply other threads:[~2026-07-30 1:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 2:53 [PATCH 0/3] Remove old AES-GCM library Eric Biggers
2026-07-22 2:53 ` [PATCH 1/3] x86/sev: Use new " Eric Biggers
2026-07-22 2:53 ` [PATCH 2/3] x86/sev: Remove obsolete virtual address check Eric Biggers
2026-07-22 10:01 ` Ard Biesheuvel
2026-07-22 15:16 ` Eric Biggers
2026-07-22 2:53 ` [PATCH 3/3] lib/crypto: aesgcm: Remove old AES-GCM library Eric Biggers
2026-07-22 9:59 ` [PATCH 0/3] " Ard Biesheuvel
2026-07-22 16:03 ` Borislav Petkov
2026-07-23 6:14 ` Nikunj A. Dadhania
2026-07-30 1:37 ` 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=20260730013708.GA91995@quark \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=aik@amd.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=clopez@suse.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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 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.