Re: Patch pre-submission to Sashiko

[Arnaldo Melo <arnaldo.melo@gmail.com>]

On October 17, 2026 3:20:47 PM GMT-03:00, Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
>On Sat Oct 17, 2026 at 5:28 PM UTC, Jiri Kosina wrote:
>>
>> [ in the spirit of the concluding discussion at this year's maintainers 
>>   summit,  I'm using this list outside of actual maintainer summit 
>>   planning :) ]
>>
>> I have just received a v1 to v11 patchset submission within roughly one 
>> day timeframe.
>>
>> Neither myself nor anyone else did comment with any review feedback, 
>> except for Sashiko. Which I believe is what triggered all the immediate 
>> resubmissions.
>>
>> I don't think this is sustanable.
>
>I think it's just fine. I encourage developers to keep the spam going.

Yay, agreed, it's not like before AI people were reading all of lkml (or other voluminous lists) traffic, just ignore what clearly is a conversation that now happens way faster than in the past until you see it calmed down 

The problem was not getting feedback at all, now people complain that feedback is being provided timely and then that people are responding to feedback in a timely fashion?

>You can simulate github style squah of v1->v2->v3 in your inbox.
>Ask your agent to monitor inbox, archive vN when vN+1 arrives
>and summarize v1->vN discussion. Then you'll always have the latest
>patch set to look at and a summary of what happened when you were away.
>Then sit on it for a day or a week to see whether respin
>cycle has ended (and bots stopped talking to each other) and then
>do a human part of maintainership.

+5, +1 is not enough 8-)

Fight fire with fire,  more is good, if it's too much look just at the latest patch series version when you think it slowed down. Or, if not allergic to AI, use it to summarize the previous discussion, human or trained on human data one.

When not understanding about some specific part of the latest version maybe looking at the "churn" will provide all the details you need.

- Arnaldo