From: Greg KH <gregkh@linuxfoundation.org>
To: tools@kernel.org
Subject: odd b4 "Mail:" trailer added for USB patch
Date: Fri, 6 Feb 2026 11:21:43 +0100 [thread overview]
Message-ID: <2026020637-cleft-viscosity-c984@gregkh> (raw)
In-Reply-To: <20191024205803.qdn6p32iyj5rqvc6@chatter.i7.local>
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)
---
✓ Signed: DKIM/phytec.de
---
Total patches: 1
---
Link: https://patch.msgid.link/20260206-wip-jremmet-hd3ss3220_vbus_split-v4-1-ee5b4e402187@phytec.de
Base: applies clean to current tree
Applying: usb: typec: hd3ss3220: Check if regulator needs to be switched
It's that odd "Mail:" header being added, which then shows up in the
commit itself:
Fixes: 27fbc19e52b9 ("usb: typec: hd3ss3220: Enable VBUS based on role state")
Signed-off-by: Jan Remmet <j.remmet@phytec.de>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linu.intel.com>
Fixes: 7e7025811579 ("usb: typec: hd3ss3220: Check if regulator needs to ^M be switched")
Mail: j.remmet@pyhtec.de
Link: https://patch.msgid.link/20260206-wip-jremmet-hd3ss3220_vbus_split-v4-1-ee5b4e402187@phytec.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Along with the extra "^M" in there (actual character) in the Fixes tag?
I'm using the latest git version of b4:
$ b4 --version
0.15-dev-47773
Any ideas?
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-06 10:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 20:58 Tooling and workflows meeting at OSS EU Lyon Konstantin Ryabitsev
[not found] ` <<20191024205803.qdn6p32iyj5rqvc6@chatter.i7.local>
2019-10-25 6:58 ` Nicolas Belouin
2019-10-25 11:16 ` Laurent Pinchart
2019-10-25 11:20 ` Dmitry Vyukov
2019-10-25 12:24 ` Veronika Kabatova
2019-10-25 13:36 ` Konstantin Ryabitsev
2019-10-25 14:15 ` Veronika Kabatova
2019-10-26 12:00 ` Kevin Hilman
2019-10-28 9:25 ` Konstantin Ryabitsev
2019-10-28 10:03 ` Konstantin Ryabitsev
2019-10-28 11:42 ` Frank Rowand
2026-02-06 10:21 ` Greg KH [this message]
2026-02-06 14:32 ` odd b4 "Mail:" trailer added for USB patch Konstantin Ryabitsev
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=2026020637-cleft-viscosity-c984@gregkh \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.