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>
Subject: Re: [PATCH] lib/crypto: arm, arm64: Drop filenames from file comments
Date: Mon, 3 Nov 2025 09:35:09 -0800 [thread overview]
Message-ID: <20251103173509.GG1735@sol> (raw)
In-Reply-To: <20251102014809.170713-1-ebiggers@kernel.org>
On Sat, Nov 01, 2025 at 06:48:06PM -0700, Eric Biggers wrote:
> Remove self-references to filenames from assembly files in
> lib/crypto/arm/ and lib/crypto/arm64/. This follows the recommended
> practice and eliminates an outdated reference to sha2-ce-core.S.
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
>
> This patch is targeting libcrypto-next
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=libcrypto-next
- Eric
next prev parent reply other threads:[~2025-11-03 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 1:48 [PATCH] lib/crypto: arm, arm64: Drop filenames from file comments Eric Biggers
2025-11-03 8:15 ` Ard Biesheuvel
2025-11-03 17:35 ` Eric Biggers [this message]
2025-11-03 18:16 ` Eric Biggers
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=20251103173509.GG1735@sol \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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