From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
Lorenzo Stoakes <ljs@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: Fri, 24 Jul 2026 20:17:07 +0200 [thread overview]
Message-ID: <20260724201707.54ea4778@foz.lan> (raw)
In-Reply-To: <20260722-accurate-defiant-puma-a7e23b@meerkat>
On Wed, 22 Jul 2026 16:48:03 -0400
Konstantin Ryabitsev <mricon@kernel.org> 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'm fine with either way.
Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Regards,
Mauro
next prev parent reply other threads:[~2026-07-24 18:17 UTC|newest]
Thread overview: 4+ 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 [this message]
2026-07-24 19:15 ` [tech-board] " David Hildenbrand (Arm)
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=20260724201707.54ea4778@foz.lan \
--to=mchehab+huawei@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.