From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org
Subject: b4 review can't use merge strategy when skipping patches
Date: Wed, 10 Jun 2026 00:36:17 +0100 [thread overview]
Message-ID: <aiijcYQInbjJ3kT4@sirena.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
Hi,
It's kind of annoying that b4 review can't use the merge strategy when
applying a series that has skipped patches in it, it means there's no
way to include a cover letter even if that cover letter is very good.
Skipping is very common with multi-subsystem serieses, especially when
DTS updates for some SoC or board are included along with a new driver.
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-06-09 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 23:36 Mark Brown [this message]
2026-06-10 15:56 ` b4 review can't use merge strategy when skipping patches Konstantin Ryabitsev
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=aiijcYQInbjJ3kT4@sirena.co.uk \
--to=broonie@kernel.org \
--cc=konstantin@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