[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250730132527.69617dbb@gandalf.local.home>
Date: Wed, 30 Jul 2025 13:25:27 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Sasha Levin <sashal@...nel.org>
Cc: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, Greg KH <greg@...ah.com>,
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 13:12:54 -0400
Sasha Levin <sashal@...nel.org> wrote:
> >>
> >> Some sort of a "traffic light" system:
> >>
> >> 1. Green: the subsystem is happy to receive patches from any source.
> >>
> >> 2. Yellow: "If you're unfamiliar with the subsystem and using any
> >> tooling to generate your patches, please have a reviewed-by from a
> >> trusted developer before sending your patch".
> >>
> >> 3. No tool-generated patches without prior maintainer approval.
> >
Actually, I'm not sure I care for the above, because honestly, I wouldn't
know which to set my subsystem to. It would be a case by case basis.
Sometimes I'm fine with the automated tooling as I can tell that the one
using it knows what they are doing and use it as a tool.
But I have refused patches from people where it was obvious that they had
no idea of what they were doing and just submitted something because
"checkpatch" or "coccinelle" said so.
-- Steve
Powered by blists - more mailing lists