From: Sasha Levin <sashal@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-doc@vger.kernel.org, corbet@lwn.net, josh@joshtriplett.org,
kees@kernel.org, konstantin@linuxfoundation.org,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
workflows@vger.kernel.org, joe@perches.com,
rdunlap@infradead.org
Subject: Re: [PATCH v3] README: restructure with role-based documentation and guidelines
Date: Mon, 17 Nov 2025 21:24:17 -0500 [thread overview]
Message-ID: <aRvY0QbRzkh94zql@laps> (raw)
In-Reply-To: <aRvHpfke8hZ--AHF@archie.me>
On Tue, Nov 18, 2025 at 08:11:01AM +0700, Bagas Sanjaya wrote:
>On Mon, Nov 17, 2025 at 04:38:01PM -0500, Sasha Levin wrote:
>> +* Build the kernel: make defconfig && make -j$(nproc)
>
>See Documentation/admin-guide/quickly-build-trimmed-linux.rst.
ooh nice, I wasn't aware of this one.
>> +* Attribution: Agents MUST add Assisted-by tag:
>> + Format: Assisted-by: $AGENT_NAME:$MODEL_VERSION [$TOOL1] [$TOOL2] ...
>> +
>> +Examples of Proper Attribution:
>> +
>> +Good examples:
>> + Assisted-by: AI-Tool:model-version-1.0 coccinelle
>> + Assisted-by: AI-Assistant:v2.5.0
>> + Assisted-by: Code-Helper:model-2024-04-09 sparse smatch
>> + Assisted-by: ML-Agent:version-2024-11
>
>So mentioning LLM version is strictly required?
Ideally yes, it'll help us keep track of which tooling is being used, and help
us improve our workflows based on the results we're seeing from different LLMs.
Also keep in mind that these instructions will be used by the LLMs, so it
shouldn't add burden on authors.
A simple prompt of "Update the kernel version in the Makefile to 10.0 and
commit the result" with the updated README gave me the following commit:
commit b3fcd7c2ec1818e3f70c4ee9c4a6f5b210e567dc (HEAD)
Author: Sasha Levin <sashal@kernel.org>
Date: Mon Nov 17 21:21:14 2025 -0500
Makefile: Update kernel version to 10.0
Update VERSION to 10 and PATCHLEVEL to 0, and clear EXTRAVERSION
to set the kernel version to 10.0.
Assisted-by: Claude:sonnet-4-5-20250929
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-11-18 2:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 21:38 Sasha Levin
2025-11-18 1:11 ` Bagas Sanjaya
2025-11-18 2:24 ` Sasha Levin [this message]
2025-11-18 8:08 ` Geert Uytterhoeven
2025-11-18 16:35 ` Jonathan Corbet
2025-11-18 16:49 ` Kees Cook
2025-11-18 16:52 ` Sasha Levin
2025-11-18 17:42 ` 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=aRvY0QbRzkh94zql@laps \
--to=sashal@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=joe@perches.com \
--cc=josh@joshtriplett.org \
--cc=kees@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.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