linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-crypto@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Petr Pavlu <petr.pavlu@suse.com>,
	Daniel Gomez <da.gomez@kernel.org>,
	Sami Tolvanen <samitolvanen@google.com>,
	"Jason A . Donenfeld" <Jason@zx2c4.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	Stephan Mueller <smueller@chronox.de>,
	Lukas Wunner <lukas@wunner.de>,
	Ignat Korchagin <ignat@cloudflare.com>,
	keyrings@vger.kernel.org, linux-modules@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] lib/crypto: ML-DSA verification support
Date: Thu, 20 Nov 2025 22:16:25 -0800	[thread overview]
Message-ID: <20251121061625.GA1855@sol> (raw)
In-Reply-To: <2528923.1763626276@warthog.procyon.org.uk>

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@kernel.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

  reply	other threads:[~2025-11-21  6:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20  0:36 [PATCH 0/4] lib/crypto: ML-DSA verification support Eric Biggers
2025-11-20  0:36 ` [PATCH 1/4] lib/crypto: Add " Eric Biggers
2025-11-20  0:36 ` [PATCH 2/4] lib/crypto: tests: Add KUnit tests for ML-DSA Eric Biggers
2025-11-20  2:29   ` Elliott, Robert (Servers)
2025-11-20  0:36 ` [PATCH 3/4] lib/crypto: tests: Add ML-DSA-65 test cases Eric Biggers
2025-11-20  0:36 ` [PATCH 4/4] lib/crypto: tests: Add ML-DSA-87 " Eric Biggers
2025-11-20  8:11 ` [PATCH 0/4] lib/crypto: ML-DSA verification support David Howells
2025-11-21  6:16   ` Eric Biggers [this message]
2025-11-20  8:14 ` [PATCH 1/4] lib/crypto: Add " David Howells
2025-11-21  2:15   ` Eric Biggers
2025-11-20  9:10 ` David Howells
2025-11-21  0:09   ` Eric Biggers
2025-11-20 13:55 ` David Howells
2025-11-21  0:50   ` Eric Biggers
2025-11-21 12:41   ` David Howells
2025-11-21 17:14     ` Eric Biggers
2025-11-21 17:41     ` David Howells
2025-11-21 21:39   ` David Howells
2025-11-21 22:23     ` Eric Biggers
2025-11-21 22:29       ` Lukas Wunner
2025-11-21 22:48         ` 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=20251121061625.GA1855@sol \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=da.gomez@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=ignat@cloudflare.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mcgrof@kernel.org \
    --cc=petr.pavlu@suse.com \
    --cc=samitolvanen@google.com \
    --cc=smueller@chronox.de \
    /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;
as well as URLs for NNTP newsgroup(s).