From: "Arnd Bergmann" <arnd@arndb.de>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Konstantin Ryabitsev" <mricon@kernel.org>
Cc: soc@lists.linux.dev, soc <soc@kernel.org>,
"Magnus Damm" <magnus.damm@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [GIT PULL 0/4] Renesas SoC updates for v7.1
Date: Wed, 18 Mar 2026 14:12:44 +0100 [thread overview]
Message-ID: <d8365648-2ee2-40fe-b6fa-c52ed5e42f44@app.fastmail.com> (raw)
In-Reply-To: <a4cad30f-0f29-4bf6-b69d-a38ebe05828c@app.fastmail.com>
On Wed, Mar 18, 2026, at 13:56, Arnd Bergmann wrote:
> 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.
Update: this one did get marked as 'Accepted' by pwbot, and
it sent the reply, so either it's back to working correctly,
or there is something else that makes it only work sometimes:
https://patchwork.kernel.org/project/linux-soc/patch/20260316074150.GA2474723@rayden/
Arnd
prev parent reply other threads:[~2026-03-18 13:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 11:12 [GIT PULL 0/4] Renesas SoC updates for v7.1 Geert Uytterhoeven
2026-03-13 11:12 ` [GIT PULL 1/4] Renesas ARM defconfig " Geert Uytterhoeven
2026-03-13 11:12 ` [GIT PULL 2/4] Renesas driver " Geert Uytterhoeven
2026-03-13 11:12 ` [GIT PULL 3/4] Renesas DT binding " Geert Uytterhoeven
2026-03-14 11:09 ` Krzysztof Kozlowski
2026-03-16 8:51 ` Geert Uytterhoeven
2026-03-17 9:29 ` Krzysztof Kozlowski
2026-03-17 9:53 ` Krzysztof Kozlowski
2026-03-18 12:58 ` Arnd Bergmann
2026-03-13 11:13 ` [GIT PULL 4/4] Renesas DTS " Geert Uytterhoeven
2026-03-14 11:13 ` Krzysztof Kozlowski
2026-03-16 8:15 ` Geert Uytterhoeven
2026-03-14 11:23 ` Krzysztof Kozlowski
2026-03-16 8:18 ` Geert Uytterhoeven
2026-03-16 8:22 ` Krzysztof Kozlowski
2026-03-16 8:25 ` Geert Uytterhoeven
2026-03-17 8:32 ` [GIT PULL 0/4] Renesas SoC " Krzysztof Kozlowski
2026-03-17 8:46 ` Geert Uytterhoeven
2026-03-17 9:11 ` Krzysztof Kozlowski
2026-03-18 12:56 ` Arnd Bergmann
2026-03-18 13:12 ` Arnd Bergmann [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=d8365648-2ee2-40fe-b6fa-c52ed5e42f44@app.fastmail.com \
--to=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mricon@kernel.org \
--cc=soc@kernel.org \
--cc=soc@lists.linux.dev \
/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