From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>, Chris Mason <clm@meta.com>,
ksummit@lists.linux.dev, Dan Carpenter <dan.carpenter@linaro.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [MAINTAINERS / KERNEL SUMMIT] AI patch review tools
Date: Wed, 8 Oct 2025 22:33:49 +0300 [thread overview]
Message-ID: <20251008193349.GI16422@pendragon.ideasonboard.com> (raw)
In-Reply-To: <aOa7Tn0QbXwL-Ydo@x1>
On Wed, Oct 08, 2025 at 04:28:14PM -0300, Arnaldo Carvalho de Melo wrote:
> On Wed, Oct 08, 2025 at 09:08:33PM +0200, Andrew Lunn wrote:
> > > My goal for KS/MS is to discuss how to enable maintainers to use review
> > > automation tools to lower their workload.
>
> > Maintainers will want to use these tools, if they prove to be useful.
>
> Right.
>
> > But ideally, we want the developers to use these tools and fix
> > the issues before they post code for review.
>
> Sure, as before, people should try to follow the best practices before
> sending pull requests, its in the best interest of everybody.
>
> But if they do so, and I guess most will, there will be more patches
> flowing upstream, thus Chris effort, I think, right?
I'd argue there will be less patches flowing upstream, lots of v1 (and
sometimes subsequent versions) where maintainers point obvious mistakes
will be avoided. The new v1 that would end up on the list will take more
time to review than the old v1, but that's just because the new v1 will
be the old v2.
To make this happen, though, maintainers will need to be reasonably
confident that obvious mistakes will have already been fixed.
> > That reduces the maintainers workload even more. So Maintainers just
> > need to run the tools to prove that the developers have run the tools
> > and have already fixed the problems.
>
> I think tools evolve and competing tools may provide different results,
> so the more tools that are used, in all steps, there will be a greater
> chance of catching things _before_ maintainers have to look at
> something.
>
> As b4 does all sorts of checks, making sure that the patch was vetted by
> whatever automation before it hits their inboxes seems to reduce the
> number of steps maintainers will have to perform.
>
> - Arnaldo
>
> > So i'm not sure your goal is the correct long term goal. It should be
> > a tool for everybody, not just maintainers.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2025-10-08 19:33 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 17:04 [MAINTAINERS / KERNEL SUMMIT] AI patch review tools Chris Mason
2025-10-08 17:20 ` Konstantin Ryabitsev
2025-10-08 18:11 ` Sasha Levin
2025-10-08 18:35 ` Chris Mason
2025-10-08 17:57 ` Bart Van Assche
2025-10-08 18:04 ` Chris Mason
2025-10-08 18:14 ` Bart Van Assche
2025-10-08 18:42 ` Chris Mason
2025-10-08 21:08 ` Kees Cook
2025-10-09 1:37 ` Chris Mason
2025-10-08 18:33 ` Sasha Levin
2025-10-09 1:43 ` Chris Mason
2025-10-09 14:49 ` Paul E. McKenney
2025-10-08 19:08 ` Andrew Lunn
2025-10-08 19:28 ` Arnaldo Carvalho de Melo
2025-10-08 19:33 ` Laurent Pinchart [this message]
2025-10-08 19:39 ` Arnaldo Carvalho de Melo
2025-10-08 20:29 ` Andrew Lunn
2025-10-08 20:53 ` Mark Brown
2025-10-09 9:37 ` Laurent Pinchart
2025-10-09 12:48 ` Arnaldo Carvalho de Melo
2025-10-08 19:29 ` Laurent Pinchart
2025-10-08 19:50 ` Bird, Tim
2025-10-08 20:30 ` Sasha Levin
2025-10-09 12:32 ` Arnaldo Carvalho de Melo
2025-10-08 20:30 ` James Bottomley
2025-10-08 20:38 ` Bird, Tim
2025-10-08 22:21 ` Jiri Kosina
2025-10-09 9:14 ` Laurent Pinchart
2025-10-09 10:03 ` Chris Mason
2025-10-10 7:54 ` Laurent Pinchart
2025-10-10 11:40 ` James Bottomley
2025-10-10 11:53 ` Laurent Pinchart
2025-10-10 14:21 ` Steven Rostedt
2025-10-10 14:35 ` Bird, Tim
2025-10-09 14:30 ` Steven Rostedt
2025-10-09 14:51 ` Andrew Lunn
2025-10-09 15:05 ` Steven Rostedt
2025-10-10 7:59 ` Laurent Pinchart
2025-10-10 14:15 ` Bird, Tim
2025-10-10 15:07 ` Joe Perches
2025-10-10 16:01 ` checkpatch encouragement improvements (was RE: [MAINTAINERS / KERNEL SUMMIT] AI patch review tools) Bird, Tim
2025-10-10 17:11 ` Rob Herring
2025-10-10 17:33 ` Arnaldo Carvalho de Melo
2025-10-10 19:21 ` Joe Perches
2025-10-10 16:11 ` [MAINTAINERS / KERNEL SUMMIT] AI patch review tools Steven Rostedt
2025-10-10 16:47 ` Joe Perches
2025-10-10 17:42 ` Steven Rostedt
2025-10-11 10:28 ` Mark Brown
2025-10-09 16:31 ` Chris Mason
2025-10-09 17:19 ` Arnaldo Carvalho de Melo
2025-10-09 17:24 ` Arnaldo Carvalho de Melo
2025-10-09 17:31 ` Alexei Starovoitov
2025-10-09 17:47 ` Arnaldo Carvalho de Melo
2025-10-09 18:42 ` Chris Mason
2025-10-09 18:56 ` Linus Torvalds
2025-10-10 15:52 ` Mauro Carvalho Chehab
2025-10-09 14:47 ` Bird, Tim
2025-10-09 15:11 ` Andrew Lunn
2025-10-09 17:58 ` Mark Brown
2025-10-09 1:15 ` Chris Mason
2025-10-08 20:37 ` Andrew Lunn
2025-10-09 12:40 ` Arnaldo Carvalho de Melo
2025-10-09 14:52 ` Paul E. McKenney
2025-10-10 3:08 ` Krzysztof Kozlowski
2025-10-10 14:12 ` Chris Mason
2025-10-31 16:51 ` Stephen Hemminger
2025-10-14 7:16 ` Dan Carpenter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251008193349.GI16422@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=acme@kernel.org \
--cc=andrew@lunn.ch \
--cc=ast@kernel.org \
--cc=clm@meta.com \
--cc=dan.carpenter@linaro.org \
--cc=ksummit@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox