All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: b4 review not picking up v2 with prefix?
Date: Sun, 12 Jul 2026 12:06:45 +0100	[thread overview]
Message-ID: <alNzLxOk2V04cNgo@lucifer> (raw)

Hi Konstantin,

Thanks for b4 review is a great tool that I'm now integrating into my workflow
(alongside b4 for sending series which I previously... resisted :)

So maybe an edge case here, and sorry for lazy report vs. patching (just so much
to do elsewhere) but for series [0] I set a mm-hotfixes prefix via:

$ b4 prep --set-prefixes 'mm-hotfixes'

Which is a convention in mm used sometimes to highlight that a series/patch
is a hotfix.

I have the v1 tracked ([1]), but when doing an update via 'u' or 'U' in the
review tui it doesn't seem to find the v2.

To make things more complicated, I sent patches separately previously ([2]
and [3]) which I decided to combine into the series sent in [0].

$ b4 --version
0.15.2

Thanks, Lorenzo

(And yes I am using b4 review to track my own series as well as reviews :P
makes it easier for me to keep track of what I've sent also :)

[0]:https://lore.kernel.org/linux-mm/20260712-series-vmap-race-fix-v2-0-ad134cc3a12a@kernel.org/
[1]:https://lore.kernel.org/all/20260710-series-vmap-race-fix-v1-0-5b3794c113fe@kernel.org/
[2]:https://lore.kernel.org/all/20260710-fix-cpa-ptdump-race-v1-1-d898699a7417@kernel.org/
[3]:https://lore.kernel.org/all/20260710-b4-fix-non-init_mm-ptdump-v1-1-2d40982c98ec@kernel.org/

             reply	other threads:[~2026-07-12 11:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-12 11:06 Lorenzo Stoakes [this message]
2026-07-15 14:05 ` b4 review not picking up v2 with prefix? Lorenzo Stoakes (ARM)

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=alNzLxOk2V04cNgo@lucifer \
    --to=ljs@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@linux.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.