From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Joe Perches <joe@perches.com>
Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Andy Whitcroft <apw@canonical.com>,
linux-arm-msm@vger.kernel.org, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Validate committer sign-off
Date: Mon, 27 Jul 2026 20:24:50 +0200 [thread overview]
Message-ID: <86ef62b5-9896-49cd-9beb-4e7435a6324e@kernel.org> (raw)
In-Reply-To: <ameceGEbXlQNGOEt@058f6326d650>
On 27/07/2026 19:59, Bjorn Andersson wrote:
> On Sat, Jul 25, 2026 at 03:47:34PM -0700, Joe Perches wrote:
>> On Fri, 2026-07-24 at 18:56 +0000, Bjorn Andersson wrote:
>>> ```
>>> checkpatch validates the Signed-off-by trailers against the patch's
>>> author, but misses the opportunity to also validate the committer when
>>> run with --git. Maintainers therefor need third-party scripts for the
>>> final Signed-off-by check.
>>
>> I don't actually see that need as an issue for checkpatch.
>>
>> checkpatch is for patches, not things that are already committed.
>>
>
> Fair, this is only applicable for people managing/receiving/collecting
> patches - be it maintainers or people gathering patches and then resend
> them...
>
> I didn't dig deeper, but my LLM found 32 cases in the last 90 days where
> linux-next maintainers points out missing committer sobs, so it seems
> like making this check more conveniently accessible would help more than
> me.
>
>> If something like this is added, it should _only_ be used when
>> --git is on the command line.
>
> The 3rd hunk (that extracts commiter, sha1 and subject) only runs "if
> $(git)", and hence $committer (from $git_committers{$filename}) will be
> '', as such signoff_match_status($1, $committer) will not be evaluated,
> and the check will be skipped.
The issue Bjorn is trying to solve is real and as he pointed out - every
second day maintainers fail to commit properly (srsly... still!). Some
of us implemented git commit hooks [1][2], but many still don't care
enough, even though installing such commit hook is basically 30 seconds.
Four reports from Mark yesterday:
https://lore.kernel.org/linux-next/?q=signed
Therefore adding verify_signedoff features to checkpatch.pl might be
useful - maybe some maintainer workflows will improve. Or maybe having
it in tree will help them. I don't have any other idea how to encourage
other people to solve it long term - my talk in 2023 did not fix it,
Steven's and Mark's emails fix only commits but not the root cause, me
mentioning the git hook convinces one maintainer per 6 months to adopt it.
Maybe checkpatch would help people to get it right...
[1] slides from https://lpc.events/event/17/contributions/1498/
[2] verify_signedoff which I recently moved to soc-tools repo:
https://web.git.kernel.org/pub/scm/linux/kernel/git/soc/soc-tools.git/tree/verify_signedoff.sh
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-07-27 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 18:56 [PATCH] checkpatch: Validate committer sign-off Bjorn Andersson
2026-07-25 22:47 ` Joe Perches
2026-07-27 17:59 ` Bjorn Andersson
2026-07-27 18:24 ` Krzysztof Kozlowski [this message]
2026-07-28 14:28 ` Bartosz Golaszewski
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=86ef62b5-9896-49cd-9beb-4e7435a6324e@kernel.org \
--to=krzk@kernel.org \
--cc=apw@canonical.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=skhan@linuxfoundation.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