public inbox for tools@linux.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <mricon@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: tools@kernel.org
Subject: Re: Missing cover letter
Date: Tue, 24 Feb 2026 19:17:47 -0500	[thread overview]
Message-ID: <20260224-classic-wakeful-elk-2ea358@lemur> (raw)
In-Reply-To: <77c934d2-27f5-4b1a-9465-92d25858e56b@intel.com>

On Tue, Feb 24, 2026 at 01:22:47PM -0800, Dave Hansen wrote:
> b4 am doesn't seem to like my cover letter:
> 
> https://lore.kernel.org/all/20260213235119.6A9A0F80@davehans-spike.ostc.intel.com/

That's because your cover letter has [v3] but none of the patches do:

    2026-02-13 23:51 [PATCH 0/4] [v3] x86/cpu: Take Intel platform into account for old microcode checks Dave Hansen
    2026-02-13 23:51 ` [PATCH 1/4] x86/microcode: Refactor platform ID enumeration into a helper Dave Hansen
    2026-02-13 23:51 ` [PATCH 2/4] x86/cpu: Add platform ID to CPU info structure Dave Hansen
    2026-02-13 23:51 ` [PATCH 3/4] x86/cpu: Add platform ID to CPU matching structure Dave Hansen
    2026-02-13 23:51 ` [PATCH 4/4] x86/microcode: Add platform mask to Intel microcode "old" list Dave Hansen

Pretty much any assumption we try to make here is going to be wrong for some
other case, so I'm just going to politely ask to please number your patches
as git/b4/any other tool expects them. :)

-- 
KR

  parent reply	other threads:[~2026-02-25  0:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 21:22 Missing cover letter Dave Hansen
2026-02-24 22:16 ` Kees Cook
2026-02-24 23:26   ` Dave Hansen
2026-02-25  0:17 ` Konstantin Ryabitsev [this message]
2026-02-25  0:21   ` Dave Hansen

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=20260224-classic-wakeful-elk-2ea358@lemur \
    --to=mricon@kernel.org \
    --cc=dave.hansen@intel.com \
    --cc=tools@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