From: Eric Biggers <ebiggers@kernel.org>
To: Antonio Quartulli <antonio@mandelbit.com>
Cc: linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Martin Willi <martin@strongswan.org>
Subject: Re: [PATCH] lib/crypto: x86/chacha: Fix mistakes and inconsistencies in comments
Date: Thu, 12 Nov 2026 19:15:59 -0800 [thread overview]
Message-ID: <20261113031559.GC1742@sol> (raw)
In-Reply-To: <0280ecc9-fcc1-48e5-b248-4641c30e5cb5@mandelbit.com>
On Thu, Nov 12, 2026 at 11:35:45AM +0100, Antonio Quartulli wrote:
>
> Maybe you want to also fix chacha-avx512-x86_64.S:588?
>
> # x0..15 += s[0..15]
> vpaddd V16,V0,V0
>
> If I am not wrong, it'd be the only lacking the lane range now.
Done in v2.
- Eric
prev parent reply other threads:[~2026-11-13 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 3:44 [PATCH] lib/crypto: x86/chacha: Fix mistakes and inconsistencies in comments Eric Biggers
2026-11-12 10:35 ` Antonio Quartulli
2026-11-13 3:15 ` 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=20261113031559.GC1742@sol \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=antonio@mandelbit.com \
--cc=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=martin@strongswan.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