[GIT PULL 0/4] Renesas SoC updates for v7.1

[Arnd Bergmann]

On Tue, Mar 17, 2026, at 10:11, Krzysztof Kozlowski wrote:
> On 17/03/2026 09:46, Geert Uytterhoeven wrote:
>
> @Konstantin,
> I use modified Rob's script to go over patch/pull queue in Patchwork:
> https://patchwork.kernel.org/project/linux-soc/list/?state=*
>
> I deal with them one-by-one, so when I finish merging, I want to be sure
> that Patchwork status is updated, thus through the script I mark it
> "Accepted".
> Like this one:
> https://patchwork.kernel.org/project/linux-soc/patch/cover.1773399675.git.geert+renesas@glider.be/
>
> Around then - can be just before or after - I push the updated branch to
> git.kernel.org. I fear that because the pull is manually updated in
> Patchwork to "Accepted", pw-bot ignores it and does not send the
> notification.
>
> Is it feasible to change pw-bot so it will notify even if it is marked
> as "Accepted"? Or any ideas how to change the flow to have both:
> A. pw-bot reply,
> B. Be 100% sure that Patchwork status is updated (allow my manual update
> via script)?

In my experience, the pw-bot reply always happens at the same time as
the update in the patchwork state, we either get both or nothing.

The way I've used it in the past was to let pw-bot handle the replies.
If anything was missing htere, I would know that I had to send a
manual reply and update the status.

I suspect that setting the status to Accepted first would stop this
from working, but right now the pwbot interaction appears to be
broken regardless of the status update, i.e. it only handles
patches but not pull requests at all.

Konstantin, this seems to have broken around the time you modified
pwbot to handle git:// URL rewrites earlier this year. Previously
it only ever caught commit messages that had the exact same URL
as the pull request message, IIRC you said that it should now handle
the case where a git:// URL gets turned into a https:// one, but
the actual result appears to be that no pull requests get matched
at all.

    Arnd