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

[Krzysztof Kozlowski]

On 17/03/2026 09:46, Geert Uytterhoeven wrote:
> Hi Krzysztof,
> 
> On Tue, 17 Mar 2026 at 09:33, Krzysztof Kozlowski <krzk at kernel.org> wrote:
>> On Fri, Mar 13, 2026 at 12:12:56PM +0100, Geert Uytterhoeven wrote:
>>> This is my first pull request for the inclusion of Renesas SoC updates
>>> for v7.1.
>>>
>>> It consists of 4 parts:
>>
>> I think pw-bot did not reply to any of these pulls, but I applied now
>> all of them.
> 
> That is correct: no replies from the pw-bot.
> renesas-dts-for-v7.1-tag1 does not seem to be in soc/for-next yet,
> perhaps you forgot to push? No need to confirm if that is true,

I pushed for-next a bit after this email.

The workflow is far from optimal, because it has two stages:
1. Iterate over each pull email, check, merge and eventually push only
this branch,

2. Merge to for-next and document the merges for internal
accounting/tracing. I guess I could merge it after each stage (1) above.

The bigger problem is lack of replies from pw-bot.


@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)?


Best regards,
Krzysztof