public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Andy Whitcroft <apw@canonical.com>,
	Dwaipayan Ray <dwaipayanray1@gmail.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] checkpatch: add support for Assisted-by tag
Date: Wed, 11 Mar 2026 12:15:08 -0400	[thread overview]
Message-ID: <abGVDLhXxHju_Zwb@laps> (raw)
In-Reply-To: <65ad15f96429d87225867e982cd1aab2@perches.com>

On Wed, Mar 11, 2026 at 08:33:26AM -0700, Joe Perches wrote:
>On 2026-03-11 08:20, Sasha Levin wrote:
>>The Assisted-by tag was introduced in 
>>Documentation/process/coding-assistants.rst
>>for attributing AI tool contributions to kernel patches. However, 
>>checkpatch.pl
>>did not recognize this tag, causing two issues:
>[]
>>diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
>[]
>>@@ -3105,6 +3106,13 @@ sub process {
>> 				}
>> 			}
>>
>>+			# Assisted-by uses AGENT_NAME:MODEL_VERSION format, not email
>>+			if ($sign_off =~ /^Assisted-by:/i) {
>>+				if ($email !~ /^\S+:\S+/) {
>>+					WARN("BAD_SIGN_OFF",
>>+					     "Assisted-by: expects 'AGENT_NAME:MODEL_VERSION [TOOL1] 
>>[TOOL2]' format\n" . $herecurr);
>>+				}
>
>I believe you could use next instead of this odd indentation avoidance.

Let me figure it out. My perl-fu is... questionable.

-- 
Thanks,
Sasha

  reply	other threads:[~2026-03-11 16:15 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
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 [this message]
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=abGVDLhXxHju_Zwb@laps \
    --to=sashal@kernel.org \
    --cc=apw@canonical.com \
    --cc=bvanassche@acm.org \
    --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 \
    /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