Re: Linking Patchwork with Sashiko?

[Roman Gushchin <roman.gushchin@linux.dev>]

Hi Mauro!

My understanding is that some subsystems might be interested in having patchwork integration 
without Sashiko sending reviews over the email. Most notable, net. Also mptcp.

Thanks!

> On May 30, 2026, at 1:30 AM, Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> 
> Hi Derek/Konstantin/Roman,
> 
>> On Fri, 29 May 2026 11:28:29 -0400
>> Derek Barbosa <debarbos@redhat.com> wrote:
>> 
>> Hi!
>> 
>>> 
>>> Forgot to mention, but at least on media patchwork, the best is for
>>> Sashiko to send an e-mail that would allow a local script to run it.
>>> 
>>> The rationale is that patchwork permissions aren't fine-grained: only
>>> an user with a project maintainer token can update checks. Granting
>>> such permission would allow other changes at the repository, like
>>> delegating a patch, archiving it or changing its status.
>>> 
>> 
>> Thanks for the note. It will take me a minute-or-two to get up to speed here.
>> I'll reach out for any clarifying questions if that's OK :^)
> 
> I added a bot parsing tool at:
>    https://github.com/mchehab/pw_tools
> 
> And ran it at the maildir with linux-media e-mails I have locally.
> It is currently set to parse e-mails from:
> 
>    - LKP;
>    - Sysbot;
>    - Sashiko.
> 
> You can see the results at:
>    https://patchwork.linuxtv.org/project/linux-media/list/
> 
> (most of the warnings there are from my parser)
> 
> And this is how it looks when a patch with bot results is opened:
>    https://patchwork.linuxtv.org/project/linux-media/patch/20260529-milos-iris-v2-2-7a763d7195ae@pm.me/
> 
> I didn't set yet any daemon to keep this updated. As I used my own
> token, all contexts were marked with my own ID.
> 
> There is one issue with the current process: if there aren't any
> warnings on a patch, like on this example:
> 
>    https://patchwork.linuxtv.org/project/linux-media/patch/20260529154357.18066-1-mohan86108@gmail.com/
> 
> There's no way to tell if Sashiko tested such patch or not. As I
> commented with Roman in a private discussion, ideally the best
> would be if Sashiko could produce a single per-patch-series email
> that would have something similar to this:
> 
>    Subject: Re: [PATCH v3 00/13] Improve process/maintainers output
>    Reply-to: <some_id>
> 
>    Hi,
> 
>    Sashiko robot found the following potencial issues:
> 
>    Patch 1/13 (<message_id): Success
>    Patch 2/13 (<message_id): Success
>    Patch 3/13 (<message_id): Success
>    Patch 4/13 (<message_id): Success
>    Patch 5/13 (<message_id): Success
> 
>    Patch 6/13 (<message_id): Warning: https://sashiko.dev/#/patchset/...
>    - [Low] The `self.field_prev` variable is assigned but never used
>    ...
> 
>    Patch 13/13: Success
> 
>    Please check if those issues are pertinent.
> 
>    Sashiko AI review
> 
> E.g. it would contain success and warning status for each message
> ID inside a patch series. This is also ideal for me as a maintainer,
> as I can clearly see the low/mid/high issues detected by sashiko
> on a single e-mail.
> 
> Thanks,
> Mauro