Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org
Subject: Re: b4 review workflow issue with partially accepted serieses
Date: Wed, 10 Jun 2026 16:25:12 +0100	[thread overview]
Message-ID: <aimB2DACiXv6MIQk@sirena.co.uk> (raw)
In-Reply-To: <20260610-influential-wolverine-of-improvement-f01d0d@meerkat>

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

On Wed, Jun 10, 2026 at 09:46:25AM -0400, Konstantin Ryabitsev wrote:

> OK, to help me properly model the workflow, is there ever a situation in which
> you would:

> - accept patches 1-3 from v1
> - request changes for patches 4-5
> - wait for v2 with those changes
> - apply patches 4-5 from v2

> In my mind, this was always a "send a follow-up series with just those 2
> patches" -- should we even support the workflow as described above?

Yes, that's a thing that happens - usually in that case the early
patches are bugfixes related to the work done to enable some new feature
that is the main thrust of the series.  You can ask people to split
things out and model it as two separate serieses but that's a bit of
faff for something that's broadly a tooling issue.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-06-10 15:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  0:26 b4 review workflow issue with partially accepted serieses Mark Brown
2026-06-09 22:01 ` Konstantin Ryabitsev
2026-06-09 22:44   ` Mark Brown
2026-06-10 11:11   ` Mark Brown
2026-06-10 13:46     ` Konstantin Ryabitsev
2026-06-10 15:25       ` Mark Brown [this message]
2026-06-10 15:35         ` Konstantin Ryabitsev
2026-06-10 15:45           ` Mark Brown
2026-06-10 15:53             ` 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=aimB2DACiXv6MIQk@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