linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb+git@google.com>
To: linux-crypto@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	herbert@gondor.apana.org.au,  ebiggers@kernel.org,
	Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH v2 0/3] crypto: arm - drop dependency on SIMD helper
Date: Thu,  3 Apr 2025 09:19:54 +0200	[thread overview]
Message-ID: <20250403071953.2296514-5-ardb+git@google.com> (raw)

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(-)


base-commit: 99585c2192cb1ce212876e82ef01d1c98c7f4699
-- 
2.49.0.472.ge94155a9ec-goog



             reply	other threads:[~2025-04-03  7:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03  7:19 Ard Biesheuvel [this message]
2025-04-03  7:19 ` [PATCH v2 1/3] crypto: arm/aes-ce - stop using the SIMD helper 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 ` [PATCH v2 0/3] crypto: arm - drop dependency on SIMD helper Eric Biggers
2025-04-07  5:27 ` 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=20250403071953.2296514-5-ardb+git@google.com \
    --to=ardb+git@google.com \
    --cc=ardb@kernel.org \
    --cc=ebiggers@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;
as well as URLs for NNTP newsgroup(s).