From: Sasha Levin <sashal@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH 6.12] lib/crypto: arm/curve25519: Disable on CPU_BIG_ENDIAN
Date: Mon, 17 Nov 2025 11:39:59 -0500 [thread overview]
Message-ID: <aRtP3_mtZ6gqmIpU@laps> (raw)
In-Reply-To: <20251117015052.GA177915@sol>
On Sun, Nov 16, 2025 at 05:50:52PM -0800, Eric Biggers wrote:
>On Sun, Nov 16, 2025 at 08:43:12PM -0500, Sasha Levin wrote:
>> On Sun, Nov 16, 2025 at 05:25:13PM -0800, Eric Biggers wrote:
>> > On Sun, Nov 16, 2025 at 07:42:34PM -0500, Sasha Levin wrote:
>> > > On Sun, Nov 16, 2025 at 11:42:24AM -0800, Eric Biggers wrote:
>> > > > On Sun, Nov 16, 2025 at 12:19:42PM -0500, Sasha Levin wrote:
>> > > > > Subject: lib/crypto: arm/curve25519: Disable on CPU_BIG_ENDIAN
>> > > > >
>> > > > > Thanks!
>> > > >
>> > > > I assume that you meant to write something meaningful in this message.
>> > >
>> > > What else did you expect to see here?
>> >
>> > Maybe some actual information that wasn't already in the email that
>> > you're replying to? What are you trying to accomplish?
>>
>> Letting you know that your backport was queued up?
>
>Maybe you should have mentioned that then?
Oh!
Apparently if I call git-send-email with --subject, it'll still strip the first
line from the patch file.
The first line was "This patch has been queued up for the ${KERNEL_VERSION}
stable tree." :)
Thanks for pointing it out, I've fixed up the script.
--
Thanks,
Sasha
prev parent reply other threads:[~2025-11-17 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 20:29 [PATCH 6.12] lib/crypto: arm/curve25519: Disable on CPU_BIG_ENDIAN Eric Biggers
2025-11-16 17:19 ` Sasha Levin
2025-11-16 19:42 ` Eric Biggers
2025-11-17 0:42 ` Sasha Levin
2025-11-17 1:25 ` Eric Biggers
2025-11-17 1:43 ` Sasha Levin
2025-11-17 1:50 ` Eric Biggers
2025-11-17 16:39 ` Sasha Levin [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=aRtP3_mtZ6gqmIpU@laps \
--to=sashal@kernel.org \
--cc=ebiggers@kernel.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