The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>,
	Konstantin Ryabitsev <mricon@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org,
	Christian Brauner <brauner@kernel.org>,
	Jeff Layton <jlayton@kernel.org>,
	Jori Koolstra <jkoolstra@xs4all.nl>,
	Sasha Levin <sashal@kernel.org>,
	tech-board@groups.linuxfoundation.org,
	Jakub Kicinski <kuba@kernel.org>,
	workflows@vger.kernel.org
Subject: Re: [PATCH] coding-assistants: simplify attribution
Date: Tue, 4 Aug 2026 11:23:34 +0200	[thread overview]
Message-ID: <072936e0-d8fc-4960-80cd-c4fbd702b0c5@kernel.org> (raw)
In-Reply-To: <anGCdTMRCA09cDKV@lucifer>

On 8/4/26 10:10, Lorenzo Stoakes (ARM) wrote:
> On Wed, Jul 22, 2026 at 04:48:03PM -0400, Konstantin Ryabitsev wrote:
>> On Wed, Jul 22, 2026 at 02:34:40PM -0600, Jonathan Corbet wrote:
>>> -  Assisted-by: Claude:claude-3-opus coccinelle sparse
>>> +  Assisted-by: LLM coccinelle sparse
>>
>> I've been playing with this a bit, and it's pretty easy to teach the agent to
>> add a few tag-like notes as to how exactly it was used, e.g.:
>>
>>     https://git.kernel.org/pub/scm/utils/b4/b4.git/commit/?id=018b87444d32eb2ffee7cb25f0785e54aa35f7bf
>>
>> This has:
>>
>> | Assisted-by: LLM [design, codegen, tests]
>>
>> It tells us a bit more about *how* the LLM was used, without introducing the
>> advertisement or pinning exact models.
>>
>> This format should allow for multiple tool usage:
>>
>> | Assisted-by: LLM [triage, tests], coccinelle
>>
>> I don't suggest this is included in this version, but it *is* fairly
>> straightforward to add to AGENTS.md and tells reviewers just how exactly the
>> LLM was used.
> 
> I think perhaps this should be a follow-up (this stuff is so fraught that I am
> super-glad to see Christian's suggestion fly through and want to take gains
> iteratively on this :), but completely agree.
> 
> David suggested something like:
> 
> Assisted-by: LLM # < what it actually did in the patch >
> 
> So I think we're kinda aligned on that?

Once the patch from Christian is upstream I can follow up with some
changes. I was holding that back for now until there is agreement on
the LLM part.

-- 
Cheers,

David

  reply	other threads:[~2026-08-04  9:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 20:34 [PATCH] coding-assistants: simplify attribution Jonathan Corbet
2026-07-22 20:48 ` Konstantin Ryabitsev
2026-07-24 18:17   ` Mauro Carvalho Chehab
2026-08-04  8:10   ` Lorenzo Stoakes (ARM)
2026-08-04  9:23     ` David Hildenbrand (Arm) [this message]
2026-08-04 11:09     ` Jori Koolstra
2026-08-04 11:49       ` Lorenzo Stoakes (ARM)
2026-07-24 19:15 ` [tech-board] " David Hildenbrand (Arm)
2026-08-03 18:56 ` Jonathan Corbet
2026-08-03 19:50   ` [tech-board] " Miguel Ojeda
2026-08-04 15:28 ` Jeff Layton
2026-08-04 15:35   ` Jonathan Corbet

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=072936e0-d8fc-4960-80cd-c4fbd702b0c5@kernel.org \
    --to=david@kernel.org \
    --cc=brauner@kernel.org \
    --cc=corbet@lwn.net \
    --cc=jkoolstra@xs4all.nl \
    --cc=jlayton@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=mricon@kernel.org \
    --cc=sashal@kernel.org \
    --cc=tech-board@groups.linuxfoundation.org \
    --cc=workflows@vger.kernel.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