[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251121061625.GA1855@sol>
Date: Thu, 20 Nov 2025 22:16:25 -0800
From: Eric Biggers <ebiggers@...nel.org>
To: David Howells <dhowells@...hat.com>
Cc: linux-crypto@...r.kernel.org, Herbert Xu <herbert@...dor.apana.org.au>,
Luis Chamberlain <mcgrof@...nel.org>,
Petr Pavlu <petr.pavlu@...e.com>,
Daniel Gomez <da.gomez@...nel.org>,
Sami Tolvanen <samitolvanen@...gle.com>,
"Jason A . Donenfeld" <Jason@...c4.com>,
Ard Biesheuvel <ardb@...nel.org>,
Stephan Mueller <smueller@...onox.de>,
Lukas Wunner <lukas@...ner.de>,
Ignat Korchagin <ignat@...udflare.com>, keyrings@...r.kernel.org,
linux-modules@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] lib/crypto: ML-DSA verification support
On Thu, Nov 20, 2025 at 08:11:16AM +0000, David Howells wrote:
> Note that your emailed patches seem corrupt somehow, but I can fetch the git
> branch.
Works for me:
git checkout -d 10a1140107e0b98bd67d37ae7af72989dd7df00b
b4 am 20251120003653.335863-1-ebiggers@...nel.org
git am ./20251119_ebiggers_lib_crypto_ml_dsa_verification_support.mbx
10a1140107e0b98bd67d37ae7af72989dd7df00b is the base-commit listed in
the cover letter, via the --base option to 'git format-patch'. It's the
current head of libcrypto-next and is also in linux-next. Maybe you
tried applying the series to a different commit.
Anyway, using the git repo is fine too. This sort of stuff is exactly
why I usually provide a git link too.
- Eric
Powered by blists - more mailing lists