From: Eric Biggers <ebiggers@kernel.org>
To: Ard Biesheuvel <ardb+git@google.com>
Cc: linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
herbert@gondor.apana.org.au, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH v2 0/3] crypto: arm - drop dependency on SIMD helper
Date: Fri, 4 Apr 2025 19:51:58 -0700 [thread overview]
Message-ID: <20250405025158.GA175983@sol.localdomain> (raw)
In-Reply-To: <20250403071953.2296514-5-ardb+git@google.com>
On Thu, Apr 03, 2025 at 09:19:54AM +0200, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
>
> The non-SIMD fallbacks in the ARM skcipher implementations have become
> dead code now that SIMD is always allowed in the contexts where
> skciphers may be used. So remove them.
>
> While at it, remove the sync CTR helper function now that its last
> users have been dropped.
>
> v2:
> - drop unnecessary includes
> - add patch #3
>
> Ard Biesheuvel (3):
> crypto: arm/aes-ce - stop using the SIMD helper
> crypto: arm/aes-neonbs - stop using the SIMD helper
> crypto: ctr - remove unused crypto_ctr_encrypt_walk()
>
> arch/arm/crypto/Kconfig | 2 -
> arch/arm/crypto/aes-ce-glue.c | 104 ++----------------
> arch/arm/crypto/aes-neonbs-glue.c | 116 ++------------------
> include/crypto/ctr.h | 47 --------
> 4 files changed, 20 insertions(+), 249 deletions(-)
>
Reviewed-by: Eric Biggers <ebiggers@kernel.org>
- Eric
next prev parent reply other threads:[~2025-04-05 2:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 7:19 [PATCH v2 0/3] crypto: arm - drop dependency on SIMD helper Ard Biesheuvel
2025-04-03 7:19 ` [PATCH v2 1/3] crypto: arm/aes-ce - stop using the " Ard Biesheuvel
2025-04-03 7:19 ` [PATCH v2 2/3] crypto: arm/aes-neonbs " Ard Biesheuvel
2025-04-03 7:19 ` [PATCH v2 3/3] crypto: ctr - remove unused crypto_ctr_encrypt_walk() Ard Biesheuvel
2025-04-05 2:51 ` Eric Biggers [this message]
2025-04-07 5:27 ` [PATCH v2 0/3] crypto: arm - drop dependency on SIMD helper Herbert Xu
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=20250405025158.GA175983@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@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