Re: [MAINTAINERS / KERNEL SUMMIT] AI patch review tools

[Arnaldo Carvalho de Melo <acme@kernel.org>]

On Thu, Oct 09, 2025 at 12:31:48PM -0400, Chris Mason wrote:
> On 10/9/25 10:30 AM, Steven Rostedt wrote:
> > On Thu, 9 Oct 2025 12:14:05 +0300 Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:

> >> Forcing contributors to pay for access to proprietary tools is not
> >> acceptable. Forcing contributors to even run proprietary tools is not
> >> acceptable. If maintainers want contributions to go through any
> >> proprietary tooling before submission, then this has to run on the
> >> maintainer side (be it on a maintainer's machine, in some form of CI, or
> >> somewhere else).
> 
> > One way I see this working is to attach it to patchwork. Sending a patch to
> > the BPF mailing list has their patchwork trigger a bunch of tests and it
> > will tell you if it passed or failed. I'm assuming if it failed, it doesn't
> > add it to patchwork and the maintainers will ignore it.
 
> > Attaching AI to patchwork could be useful as well. But this would run on
> > some server that someone will have to pay for. But it will not be the
> > submitter.
 
> Just to clarify, that's what already happens with BPF today.
 
> Ex: https://github.com/kernel-patches/bpf/pull/9962 are all from the
> review prompts.

This almost relieves me from the guilt not to have reviewed that series
from Alan ;-\

- Arnaldo