Re: Patch pre-submission to Sashiko

[Rodrigo Vivi <rodrigo.vivi@intel.com>]

On Mon, Oct 19, 2026 at 08:57:23AM -0400, Julia Lawall wrote:
> 
> 
> > On 19 Oct 2026, at 08:46, Michal Simek <monstr@monstr.eu> wrote:
> > 
> > 
> > 
> >> On 10/19/26 14:02, Julia Lawall wrote:
> >>> On Mon, 19 Oct 2026, Michal Simek wrote:
> >>> 
> >>> 
> >>> On 10/19/26 09:26, David Woodhouse wrote:
> >>>> On Mon, 2026-10-19 at 08:25 +0200, Krzysztof Kozlowski wrote:
> >>>>> I assume you mean they will be running it through Sashiko
> >>>>> infrastructure, so using sponsored tokens. Otherwise that possibility is
> >>>>> already there - you can run Sashiko, just a matter of money.
> >>>> 
> >>>> I have a patchset in flight where I *have* been running Sashiko (as
> >>>> well as lots of self-tests) locally, and then got further feedback on
> >>>> the list from the public Sashiko which my own run hadn't seen. Twice.
> >>>> 
> >>>> I still need to send v3...
> >>> 
> >>> Isn't it better to create a new mailing list and filter all CCs/To?
> >>> People can send patches to that mailing list and get reply without CCing
> >>> maintainers and mailing lists. They can run a lot of iterations like that.
> >>> When it is clear they can send clear v1 in a normal way.
> >> This isn't just free tokens for anyone who wants to make a change to the
> >> Linux kernel, not necessarily a change that will ever be sent to a
> >> maintainer?
> > Isn't this something what people can do even now? They will only keep mailing list and maintainer in CC.
> 
> There is still the illusion that the code risks ending up in the kernel. I guess that even with the Sashiko only list the code is still public, so perhaps that is dissuasive.

Perhaps if there was some way to point out to Sashiko where the github for that
series is and some button to request redo-review, then the polution on the
mailing list doesn't exist while dev isn't sure that the Sashiko is okay
with the changes.

The problem with this idea might be the abuse of the tokens indeed.

I also believe that the delayed Sashiko response is not good and it only
makes the pain longer.

Local runs of Sashiko might also not cover everything because of tokens
or models limitation. Then, there will always be the risk of local limited
setup not catching the same things and the loop in public mailing list to
continue.

> 
> 
> > 
> > Thanks,
> > Michal
> > 
> > --
> > Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
> > w: www.monstr.eu p: +42-0-721842854
> > Maintainer of Linux kernel - Xilinx Microblaze
> > Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP/Versal ARM64 SoCs
> > U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal/Versal NET SoCs
> > TF-A maintainer - Xilinx ZynqMP/Versal/Versal NET SoCs
> > 
> 
>