Re: [RFC] Mitigating Sashiko-driven iteration noise on the main MPTCP list

[Matthieu Baerts <matttbe@kernel.org>]

Hi Gang,

On 04/09/2026 09:25, gang.yan@linux.dev wrote:
> September 3, 2026 at 5:52 PM, "Matthieu Baerts" <matttbe@kernel.org mailto:matttbe@kernel.org?to=%22Matthieu%20Baerts%22%20%3Cmatttbe%40kernel.org%3E > wrote:

(...)

>> In conclusion, I don't think we want a "hidden" ML, but we do want to
>> reduce the traffic on the ML, and the recommended solution is to push
>> people validating their patches with the same tool (or closed to, if
>> possible) before any submissions. WDYT?
> 
> I now see that my idea was probably too naive/overly simplistic :)
> 
> I have tried deploying Sashiko locally

Thank you for having done that.

> and noticed that different models can produce quite different review outputs.

Yes indeed, and from what I understood, even the same model can produce
different results. But I think that's fine, and I hope various models
out there can at least spot "simple" / "important" issues. So even if
the model(s) you can access to is/are "not as precise/picky" as the
Google one, that's still good to have a such pre-checks being done to
reduce the number of iterations.

Note that Clashiko is running multiple models and doing cross reviews.
In theory, that sounds good to have less false positives (but then, it
seems to be very/too picky as well...). So at the end, it seems like a
good thing to have access to various models to cross checks the reviews.

Cheers,
Matt