Linux Kernel Summit discussions
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Jason Gunthorpe <jgg@nvidia.com>,
	ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] The place of AI code review in the Linux Kernel process
Date: Thu, 23 Jul 2026 08:50:02 +0200	[thread overview]
Message-ID: <20260723084954.42e6a6e4@foz.lan> (raw)
In-Reply-To: <efdce5c5-13a1-4dec-9823-bb2a37084538@roeck-us.net>

On Sat, 18 Jul 2026 07:14:02 -0700
Guenter Roeck <linux@roeck-us.net> wrote:

> On 7/17/26 18:17, Linus Torvalds wrote:
...
> > And I think that when there is AI review, people are less likely to
> > see it as a positive thing when the AI then points out pre-existing
> > problems.
> >   
> 
> I agree, and I have seen that pattern.
> 
> I do not expect patch authors to fix pre-existing issues in my
> scope of responsibility, though I appreciate it if they do it.
> I actually asked Roman if it would be possible to add a per-subsystem
> prompt to Sashiko's reply. That would let me inform authors that
> I do not mandate fixing such issues.

IMO, instead of using a prompt to add per-subsystem instructions
is a token waste and it is prone to errors, as LLMs might fall
adding it or and modifying it.

A much simpler approach would be to have something like this:

	https://github.com/sashiko-dev/sashiko/pull/364
	(build-tested only)

adding a body prefix on the top of the e-mails, set via sashiko.dev
email policy.

Thanks,
Mauro

  parent reply	other threads:[~2026-07-23  6:50 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 16:55 [MAINTAINERS SUMMIT] The place of AI code review in the Linux Kernel process Roman Gushchin
2026-07-15 17:51 ` Miguel Ojeda
2026-07-15 21:37   ` Roman Gushchin
2026-07-17  6:43     ` Ben Copeland
2026-07-16 15:32   ` Sasha Levin
2026-07-15 17:56 ` Mauro Carvalho Chehab
2026-07-15 18:57 ` Jason Gunthorpe
2026-07-15 21:21   ` Roman Gushchin
2026-07-16 22:26     ` Mauro Carvalho Chehab
2026-07-17 23:17     ` Linus Torvalds
2026-07-18  0:01       ` Mark Brown
2026-07-18  1:09       ` Laurent Pinchart
2026-07-18  1:17         ` Linus Torvalds
2026-07-18 13:38           ` Arnaldo Melo
2026-07-18 14:14           ` Guenter Roeck
2026-07-18 16:15             ` SJ Park
2026-07-23  6:50             ` Mauro Carvalho Chehab [this message]
2026-07-23 14:34               ` Guenter Roeck
2026-07-23 14:59                 ` Mark Brown
2026-07-23 17:08                   ` Rodrigo Vivi
2026-07-23 17:33                     ` Mark Brown
2026-07-23 17:27                   ` Guenter Roeck
2026-07-24  0:08                     ` Tomasz Figa
2026-07-24 12:25                       ` Steven Rostedt
2026-07-24 13:05                       ` James Bottomley
2026-07-18 16:13       ` Jason Gunthorpe
2026-07-15 19:45 ` Dmitry Torokhov
2026-07-16  0:03 ` Steven Rostedt
2026-07-16  0:30 ` SJ Park
2026-07-17 21:05 ` Krzysztof Kozlowski
2026-07-17 21:14   ` Roman Gushchin
2026-07-23  7:13     ` Mauro Carvalho Chehab

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=20260723084954.42e6a6e4@foz.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=jgg@nvidia.com \
    --cc=ksummit@lists.linux.dev \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux@roeck-us.net \
    --cc=roman.gushchin@linux.dev \
    --cc=torvalds@linux-foundation.org \
    /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