[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250730121829.0c89228d@gandalf.local.home>
Date: Wed, 30 Jul 2025 12:18:29 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: Greg KH <greg@...ah.com>, Sasha Levin <sashal@...nel.org>,
corbet@....net, linux-doc@...r.kernel.org, workflows@...r.kernel.org,
josh@...htriplett.org, kees@...nel.org, konstantin@...uxfoundation.org,
linux-kernel@...r.kernel.org, Linus Torvalds
<torvalds@...ux-foundation.org>, "Dr. David Alan Gilbert"
<linux@...blig.org>
Subject: Re: [PATCH 0/4] Add agent coding assistant configuration to Linux
kernel
On Wed, 30 Jul 2025 16:34:28 +0100
Lorenzo Stoakes <lorenzo.stoakes@...cle.com> wrote:
> > Which looked like someone else (now Cc'd on this thread) took it public,
> > and I wanted to see where that ended. I didn't want to start another
> > discussion when there's already two in progress.
>
> OK, but having a document like this is not in my view optional - we must
> have a clear, stated policy and one which ideally makes plain that it's
> opt-in and maintainers may choose not to take these patches.
That sounds pretty much exactly as what I was stating in our meeting. That
is, it is OK to submit a patch written with AI but you must disclose it. It
is also the right of the Maintainer to refuse to take any patch that was
written in AI. They may feel that they want someone who fully understands
what that patch does, and AI can cloud the knowledge of that patch from the
author.
I guess a statement in submitting-patches.rst would suffice, or should it
be a separate standalone document?
-- Steve
Powered by blists - more mailing lists