From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Kernel.org Tools" <tools@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor@kernel.org>
Subject: Re: review-tui: Handle different Patchwork current statuses
Date: Thu, 24 Sep 2026 14:53:31 +0200 [thread overview]
Message-ID: <4d64b396-3d06-4356-b5f6-1599e9e3f4f0@kernel.org> (raw)
In-Reply-To: <643cb7a7-d817-441b-913f-7f78e7710e5c@kernel.org>
On 24/09/2026 14:52, Krzysztof Kozlowski wrote:
> Hey,
>
> I am trying to adapt b4 review to DT workflow with DT patchwork and I
> think interpretation of current patch status needs customization. I have
> in .gitconfig:
>
> [b4]
> pw-review-state = needs-ack
> pw-accept-state = not-applicable
> pw-discard-state = changes-requested
>
> But b4 review tui in Patchwork status does not show any patches under
> Needs ACK.
>
> https://patchwork.kernel.org/project/devicetree/list/
>
> To recap, our statuses are used like:
> 0. "New": not processed by any automation
> 1. "Under Review": being processed by automation
> 2. "Needs ACK": Actually waiting for our review or being reviewed. This
> is what we want to see in list of patches.
> 3. "Changes requested": Patch rejected with changes needed
> 4. "Not applicable": Patch was reviewed but handled elsewhere as most of
> work is like that.
>
> Either I miss some .gitconfig options or b4 is missing such
> customization. If the latter, can you add a feature-request for this? I
> would like to adopt b4 and move away from our internal scripting...
>
Ah, and if that matters: b4 v0.16.0
Best regards,
Krzysztof
prev parent reply other threads:[~2026-09-24 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 12:52 review-tui: Handle different Patchwork current statuses Krzysztof Kozlowski
2026-09-24 12:53 ` Krzysztof Kozlowski [this message]
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=4d64b396-3d06-4356-b5f6-1599e9e3f4f0@kernel.org \
--to=krzk@kernel.org \
--cc=conor@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=robh@kernel.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