From: Konstantin Ryabitsev <mricon@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: tools@kernel.org
Subject: Re: odd b4 "Mail:" trailer added for USB patch
Date: Fri, 6 Feb 2026 09:32:05 -0500 [thread overview]
Message-ID: <20260206-mighty-blond-ferret-e7bdb9@lemur> (raw)
In-Reply-To: <2026020637-cleft-viscosity-c984@gregkh>
On Fri, Feb 06, 2026 at 11:21:43AM +0100, Greg KH wrote:
> When running the following command that I normally do to apply patches:
> b4 am -S -t -o - | git am -s
> from my email client, for the patch with:
> Message-ID: <20260206-wip-jremmet-hd3ss3220_vbus_split-v4-1-ee5b4e402187@phytec.de>
>
> I get:
>
> Looking up https://lore.kernel.org/all/20260206-wip-jremmet-hd3ss3220_vbus_split-v4-1-ee5b4e402187@phytec.de/
> Analyzing 1 messages in the thread
> Analyzing 11 code-review messages
> Checking attestation on all messages, may take a moment...
> ---
> ✓ [PATCH v4] usb: typec: hd3ss3220: Check if regulator needs to be switched
> be switched") (✓ DKIM/phytec.de)typec: hd3ss3220: Check if regulator needs to
> + Mail: j.remmet@pyhtec.de (✓ DKIM/phytec.de)
Sigh. This happens occasionally, because we can't have a strict list of
trailers we recognize for follow-ups (because of people's proclivity to use
things like Suggested-and-co-developed-by: or whatnot). We have a junklist of
things we know are bogus, but every now and again there's something we haven't
thought of (like people using "Mail" instead of "Email").
I'll add this to the junklist as well.
-K
next prev parent reply other threads:[~2026-02-06 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191024205803.qdn6p32iyj5rqvc6@chatter.i7.local>
2026-02-06 10:21 ` odd b4 "Mail:" trailer added for USB patch Greg KH
2026-02-06 14:32 ` Konstantin Ryabitsev [this message]
2026-03-06 0:23 ` Konstantin Ryabitsev
2026-03-06 0:25 ` B4 Bugbot
2026-03-06 19:34 ` B4 Bugbot
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=20260206-mighty-blond-ferret-e7bdb9@lemur \
--to=mricon@kernel.org \
--cc=gregkh@linuxfoundation.org \
--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