From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Jason A . Donenfeld " <Jason@zx2c4.com>,
Ard Biesheuvel <ardb@kernel.org>,
x86@kernel.org
Subject: Re: [PATCH] lib/crypto: x86/sha512: Remove unnecessary checks for nblocks==0
Date: Mon, 23 Jun 2025 19:45:39 -0700 [thread overview]
Message-ID: <20250624024539.GB7127@sol> (raw)
In-Reply-To: <20250621021549.105357-1-ebiggers@kernel.org>
On Fri, Jun 20, 2025 at 07:15:49PM -0700, Eric Biggers wrote:
> Since sha512_blocks() is called only with nblocks >= 1, remove
> unnecessary checks for nblocks == 0 from the x86 SHA-512 assembly code.
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
> lib/crypto/x86/sha512-avx-asm.S | 6 +-----
> lib/crypto/x86/sha512-avx2-asm.S | 5 +----
> lib/crypto/x86/sha512-ssse3-asm.S | 6 +-----
> 3 files changed, 3 insertions(+), 14 deletions(-)
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=libcrypto-next
- Eric
prev parent reply other threads:[~2025-06-24 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 2:15 [PATCH] lib/crypto: x86/sha512: Remove unnecessary checks for nblocks==0 Eric Biggers
2025-06-24 2:45 ` 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=20250624024539.GB7127@sol \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox