public inbox for tools@linux.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: users@kernel.org, tools@kernel.org
Subject: Re: b4 review available in master
Date: Wed, 4 Mar 2026 21:38:09 +0000	[thread overview]
Message-ID: <20260304-deviancy-overlaid-e7947f09089c@spud> (raw)
In-Reply-To: <20260303-tactful-zippy-oxpecker-fbcadd@lemur>

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

On Tue, Mar 03, 2026 at 12:16:18AM -0500, Konstantin Ryabitsev wrote:
> On Sat, Feb 28, 2026 at 10:32:04PM +0000, Conor Dooley wrote:

> > I feel like I am spamming you with responses here, sorry about that!
> 
> Please continue! There's also a hopefully-noticeable notification when you're
> running the review tui from a review branch that will tell you how to get back
> to the series tracking view. :)

I tried again today to use it but ran into some things flow wise, that
prevented me from actually doing any reviewing.

Firstly, with the patchwork pane, how do I determine which states
appear? Most things get set by a bot to "needs ack" in the dt patchwork,
but I only see things as "under review" or "new" in the pane. We use
"under review" to mean the bot is looking at it mainly and "needs ack"
for stuff that humans need to look at, so I need to figure out how to
display things with that status. Pretty much this is "your default view
doesn't match the default patchwork view (State = Action Required)".

Secondly, if I'm working from a patchwork, it'd be really great if I
could reply to patches directly from the patchwork pane. 90% of patches
I review (or more) I do not need to apply, so working in mutt is
significantly faster than having to track, then open in a different
pane. Related to that, being able to display the patchwork pane
per-patch as an option would be a wishlist item to make this replace
mutt for me.

That's from a dt-bindings review perspective though, how these things
work is fine (bugs aside) where I am the person applying patches. It's
probably far from the end of the world if dt-binding stuff stays in
mutt, since it's probably atypical.

Oh, and I managed to trigger a formatting bug again, on 0.15-dev-54639

	MissingStyle: Failed to get style 'v2,1/2'; unable to parse 'v2,1/2' as color; 'v2,1/2' is not a valid color

after grabbing a series from patchwork

	/stuff/b4/b4.sh review tui -i linux-dt
	Retrieving series: <20260212082105.1878720-2-sh86.bae@samsung.com>

It creates a massive spam of text, but it contains:
	text = <text 'Started tracking:  dt-bindings: soc: samsung: exynos-sysreg: Add hsi0 for ExynosAutov920' [Span(18, 88, 'v2,1/2')] ''>

LMK if you require the full log for this.

Pretty sure I replicated it on 0.15-dev-18f8f too, but I'm not entirely
sure as I cannot untrack series to retest.

I also hit some weird interaction, where after hitting track on a load
of stuff in the patchwork pane, nothing shows up in my review pane, but
it looks like it should have appeared:
	/stuff/b4/b4.sh review tui -i linux-dt
	Retrieving series: <20260220-ayn-vendor-v1-1-292cbbb682b3@gmail.com>
	Looking up https://lore.kernel.org/all/20260220-ayn-vendor-v1-1-292cbbb682b3@gmail.com/
	Grabbing thread from lore.kernel.org/all/20260220-ayn-vendor-v1-1-292cbbb682b3@gmail.com/t.mbox.gz

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

  reply	other threads:[~2026-03-04 21:38 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 19:53 b4 review available in master Konstantin Ryabitsev
2026-02-28 15:12 ` Mark Brown
2026-02-28 15:47   ` Konstantin Ryabitsev
2026-02-28 16:00     ` Konstantin Ryabitsev
2026-02-28 18:12       ` Mark Brown
2026-02-28 15:53 ` Mark Brown
2026-02-28 21:11   ` Mark Brown
2026-03-03  5:14     ` Konstantin Ryabitsev
2026-03-03 12:42       ` Mark Brown
2026-03-03 18:21         ` Konstantin Ryabitsev
2026-03-12 17:21           ` Alexandre Belloni
2026-03-13 15:42             ` Konstantin Ryabitsev
2026-03-13 15:55               ` Alexandre Belloni
2026-03-21 10:01                 ` Alexandre Belloni
2026-03-12 17:35           ` Mark Brown
2026-03-13 15:42             ` Konstantin Ryabitsev
2026-02-28 16:36 ` Conor Dooley
2026-02-28 16:45   ` Konstantin Ryabitsev
2026-02-28 16:48     ` Conor Dooley
2026-02-28 16:57       ` Konstantin Ryabitsev
2026-02-28 17:00         ` Conor Dooley
2026-02-28 17:05           ` Konstantin Ryabitsev
2026-02-28 17:12             ` Conor Dooley
2026-02-28 17:21               ` Konstantin Ryabitsev
2026-02-28 17:34                 ` Konstantin Ryabitsev
2026-02-28 18:37                   ` Conor Dooley
2026-02-28 22:16                   ` Conor Dooley
2026-02-28 22:32                     ` Conor Dooley
2026-03-03  5:16                       ` Konstantin Ryabitsev
2026-03-04 21:38                         ` Conor Dooley [this message]
2026-03-04 22:40                           ` Konstantin Ryabitsev
2026-03-04 22:55                             ` Conor Dooley
2026-03-05  3:26                               ` Konstantin Ryabitsev
2026-03-05  6:17                             ` Konstantin Ryabitsev
2026-02-28 18:31 ` Michael S. Tsirkin
2026-02-28 20:06   ` Konstantin Ryabitsev
2026-02-28 20:23     ` Michael S. Tsirkin
2026-02-28 20:37       ` Konstantin Ryabitsev
2026-02-28 20:47         ` Michael S. Tsirkin
2026-02-28 20:53           ` Konstantin Ryabitsev
2026-02-28 21:04             ` Michael S. Tsirkin
2026-03-02  9:30 ` Michael S. Tsirkin
2026-03-02 10:33 ` Michael S. Tsirkin
2026-03-03  1:58 ` Junio C Hamano
2026-03-03  4:26   ` Konstantin Ryabitsev
2026-03-03 11:20     ` Matthieu Baerts
2026-03-04 20:56 ` range-diff hangs Marc Kleine-Budde
2026-03-14  4:20   ` Konstantin Ryabitsev
2026-03-14  9:27     ` Marc Kleine-Budde
2026-03-16 23:28 ` b4 review available in master Jonathan Corbet
2026-03-16 23:41   ` Jonathan Corbet
2026-03-17  0:15     ` Konstantin Ryabitsev
2026-03-17 14:11       ` Jonathan Corbet
2026-03-17 14:23         ` Konstantin Ryabitsev
2026-03-17 20:30           ` Konstantin Ryabitsev
2026-03-17 21:46             ` Jonathan Corbet
2026-03-17 22:39               ` Konstantin Ryabitsev
2026-03-17 23:37                 ` Konstantin Ryabitsev
2026-03-18  7:56                   ` Geert Uytterhoeven
2026-03-18 13:00                     ` Mark Brown
2026-03-18 13:26                     ` Konstantin Ryabitsev
2026-03-18 16:47                   ` Jonathan Corbet
2026-03-18 18:31                     ` Laurent Pinchart
2026-03-18 19:22                     ` Konstantin Ryabitsev
2026-03-17  0:12   ` Konstantin Ryabitsev
2026-03-18 13:43   ` Johannes Thumshirn
2026-03-20 16:53 ` Louis Chauvet
2026-03-20 19:31   ` Konstantin Ryabitsev
2026-03-20 21:14     ` Alexandre Belloni

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=20260304-deviancy-overlaid-e7947f09089c@spud \
    --to=conor@kernel.org \
    --cc=mricon@kernel.org \
    --cc=tools@kernel.org \
    --cc=users@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