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: <77782f57-6131-4968-95dc-088329cc50f7@kernel.org>
Date: Sat, 26 Jul 2025 04:07:40 -0500
From: Mario Limonciello <superm1@...nel.org>
To: Sasha Levin <sashal@...nel.org>, workflows@...r.kernel.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: rostedt@...dmis.org, kees@...nel.org, konstantin@...uxfoundation.org,
 corbet@....net, josh@...htriplett.org
Subject: Re: [RFC 0/2] Add AI coding assistant configuration to Linux kernel

> Example patch creation with Claude Code:
> 
> 	$ claude -p "Fix the dont -> don't typo in @Documentation/power/opp.rst. Commit the result"
> 	Done! The typo has been fixed and committed.

Is this actually how people use AI agents?  I've never thought of asking 
an agent to write a whole patch and commit the result.

The way that I've seen it is things like Github Copilot within VScode 
where there are inline suggestions.  It's kinda like clangd except it 
suggests corrections to your mistakes instead of just underlining them 
with red squiggles.

Like if you messed up the argument and passed a pointer when it was 
supposed to be a pointer to a pointer it will give you a little tooltip 
correction.  But this is long before you would be ready to actually 
commit a patch, heck it's before even testing it (obviously).

The actual committing action would be by running 'git commit'.  So I 
don't see how these tags could end up in there.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ