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

[Steven Rostedt <rostedt@goodmis.org>]

On Thu, 9 Oct 2025 16:51:39 +0200
Andrew Lunn <andrew@lunn.ch> wrote:

> > 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.  
> 
> Not quite, at least not for netdev, which shares some infrastructure
> with BPF. Patches get ingested into patchwork, and then some time
> later, the CI system will get them from patchwork and run the
> tests. The results are then added to patchwork, both as red/yellow/green
> traffic lights, and clickable links to the test results. Failing tests
> don't automatically cause patchwork to change the status to "Change
> Requested", a human is needed to look at the actual failures and
> decide if the patch should be rejected or not.

Thanks for the clarification. I'm just a submitter to the system and see
the feedback it gives, which looks nice (even though it's mostly irrelevant
to me as I simply Cc the bpf mailing list to let them know what I'm doing
on the tracing side).

-- Steve