From: Jonathan Corbet <corbet@lwn.net>
To: Harry Wentland <harry.wentland@amd.com>,
apw@canonical.com, joe@perches.com, linux-kernel@vger.kernel.org
Cc: dwaipayanray1@gmail.com, lukas.bulwahn@gmail.com,
Harry Wentland <harry.wentland@amd.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Alex Hung <alex.hung@amd.com>
Subject: Re: [PATCH v2] scripts/checkpatch: add Assisted-by: tag validation
Date: Fri, 27 Mar 2026 15:28:36 -0600 [thread overview]
Message-ID: <87341l6jy3.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260327154157.162962-1-harry.wentland@amd.com>
Harry Wentland <harry.wentland@amd.com> writes:
> The coding-assistants.rst documentation defines the Assisted-by: tag
> format for AI-assisted contributions as:
>
> Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]
>
> This format does not use an email address, so checkpatch currently
> reports a false positive about an invalid email when encountering this
> tag.
>
> Add Assisted-by: to the recognized signature tags and standard signature
> list. When an Assisted-by: tag is found, validate it instead of checking
> for an email address.
>
> Examples of passing tags:
> - Claude:claude-3-opus coccinelle sparse
> - FOO:BAR.baz
> - Copilot Github:claude-3-opus
> - GitHub Copilot:Claude Opus 4.6
> - My Cool Agent:v1.2.3 coccinelle sparse
>
> Examples of tags triggering the new warning:
> - Claude coccinelle sparse
> - JustAName
> - :missing-agent
>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Assisted-by: Claude:claude-opus-4.6
> Co-developed-by: Alex Hung <alex.hung@amd.com>
> Signed-off-by: Alex Hung <alex.hung@amd.com>
> Signed-off-by: Harry Wentland <harry.wentland@amd.com>
> ---
> scripts/checkpatch.pl | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
Given that people are running into this problem, and that we *do* want
people using that tag, it would make sense to go ahead and get this in,
perhaps even with a CC: stable. Would you like me to route it
Linusward, or did you have another path in mind?
Joe, does this look good to you?
Thanks,
jon
next prev parent reply other threads:[~2026-03-27 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 15:41 Harry Wentland
2026-03-27 21:28 ` Jonathan Corbet [this message]
2026-03-28 2:11 ` Joe Perches
2026-03-30 16:02 ` 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=87341l6jy3.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=alex.hung@amd.com \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=harry.wentland@amd.com \
--cc=jani.nikula@linux.intel.com \
--cc=joe@perches.com \
--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
all inboxes | Powered by JetHome®