linux-kernel - Re: [PATCH 0/4] Add agent coding assistant configuration to Linux kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250804181447.0c518b14@gandalf.local.home>
Date: Mon, 4 Aug 2025 18:14:47 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Jiri Kosina <kosina@...il.com>
Cc: Sasha Levin <sashal@...nel.org>, Michal Hocko <mhocko@...e.com>, David
 Hildenbrand <david@...hat.com>, Greg KH <gregkh@...uxfoundation.org>,
 Vlastimil Babka <vbabka@...e.cz>, 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
Subject: Re: [PATCH 0/4] Add agent coding assistant configuration to Linux
 kernel

On Tue, 5 Aug 2025 00:03:29 +0200 (CEST)
Jiri Kosina <kosina@...il.com> wrote:

> Al made a very important point somewhere earlier in this thread.
> 
> The most important (from the code quality POV) thing is -- is there a 
> person that understands the patch enough to be able to answer questions 
> (coming from some other human -- most likely reviewer/maintainer)?
> 
> That's not something that'd be reflected in DCO, but it's very important 
> fact for the maintainer's decision process.

Perhaps this is what needs to be explicitly stated in the SubmittingPatches
document.

I know we can't change the DCO, but could we add something about our policy
is that if you submit code, you certify that you understand said code, even
if (especially) it was produced by AI?

-- Steve