From: Bart Van Assche <bvanassche@acm.org>
To: Sasha Levin <sashal@kernel.org>, corbet@lwn.net
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH v2] docs: add AI Coding Assistants documentation
Date: Tue, 10 Mar 2026 09:32:28 -0700 [thread overview]
Message-ID: <2c7e0149-c178-41b8-ac5e-270bfea8b1f8@acm.org> (raw)
In-Reply-To: <20251223122110.2496946-1-sashal@kernel.org>
On 12/23/25 4:21 AM, Sasha Levin wrote:
> +Attribution
> +===========
> +
> +When AI tools contribute to kernel development, proper attribution
> +helps track the evolving role of AI in the development process.
> +Contributions should include an Assisted-by tag in the following format::
> +
> + Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]
This patch requires the use of a new tag but does not add support in
checkpatch for the new tag. Checkpatch complains about this tag. An
example is available below. Does anyone plan to add support in
checkpatch for this new tag?
Thanks,
Bart.
------------------------------------------------------------------------
$ git format-patch -1 457965c13f0837a289c9164b842d0860133f6274
0001-tracing-Add-NULL-pointer-check-to-trigger_data_free.patch
$ scripts/checkpatch.pl
0001-tracing-Add-NULL-pointer-check-to-trigger_data_free.patch
WARNING: Non-standard signature: Assisted-by:
#23:
Assisted-by: Gemini:gemini-3.1-pro
ERROR: Unrecognized email address: 'Gemini:gemini-3.1-pro'
#23:
Assisted-by: Gemini:gemini-3.1-pro
total: 1 errors, 1 warnings, 9 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or
--fix-inplace.
0001-tracing-Add-NULL-pointer-check-to-trigger_data_free.patch has style
problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
bvanassche@bvanassche:~/software/linux-kernel$ git log
Documentation/process/coding-assistants.rst
------------------------------------------------------------------------
next prev parent reply other threads:[~2026-03-10 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 1:07 [PATCH] README: add AI Coding Assistants section Sasha Levin
2025-12-22 22:04 ` Jonathan Corbet
2025-12-23 12:21 ` [PATCH v2] docs: add AI Coding Assistants documentation Sasha Levin
2025-12-23 15:25 ` Jonathan Corbet
2026-01-06 21:56 ` Jonathan Corbet
2026-03-10 16:32 ` Bart Van Assche [this message]
2026-03-11 15:20 ` [PATCH] checkpatch: add support for Assisted-by tag Sasha Levin
2026-03-11 15:33 ` Joe Perches
2026-03-11 16:15 ` Sasha Levin
2026-03-11 21:58 ` [PATCH v2] " Sasha Levin
2026-03-12 20:59 ` Joe Perches
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=2c7e0149-c178-41b8-ac5e-270bfea8b1f8@acm.org \
--to=bvanassche@acm.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=sashal@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
all inboxes | Powered by JetHome®