[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aRvY0QbRzkh94zql@laps>
Date: Mon, 17 Nov 2025 21:24:17 -0500
From: Sasha Levin <sashal@...nel.org>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: linux-doc@...r.kernel.org, corbet@....net, josh@...htriplett.org,
kees@...nel.org, konstantin@...uxfoundation.org,
linux-kernel@...r.kernel.org, rostedt@...dmis.org,
workflows@...r.kernel.org, joe@...ches.com, rdunlap@...radead.org
Subject: Re: [PATCH v3] README: restructure with role-based documentation and
guidelines
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@...nel.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
Powered by blists - more mailing lists