From: Joe Perches <joe@perches.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.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: Tue, 28 Jul 2026 09:09:50 -0700 [thread overview]
Message-ID: <e099826edfb82a4c3a0719d54261e7d070ffae04.camel@perches.com> (raw)
In-Reply-To: <86ef62b5-9896-49cd-9beb-4e7435a6324e@kernel.org>
On Mon, 2026-07-27 at 20:24 +0200, Krzysztof Kozlowski wrote:
> On 27/07/2026 19:59, 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.
[]
> 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.
[]
> Maybe checkpatch would help people to get it right...
Alright, I'll look at this proposal more thoroughly.
next prev parent reply other threads:[~2026-07-28 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 18:56 Bjorn Andersson
2026-07-25 22:47 ` Joe Perches
2026-07-27 17:59 ` Bjorn Andersson
2026-07-27 18:24 ` Krzysztof Kozlowski
2026-07-28 16:09 ` Joe Perches [this message]
2026-07-28 14:28 ` Bartosz Golaszewski
2026-07-28 16:32 ` Mark Brown
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=e099826edfb82a4c3a0719d54261e7d070ffae04.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=krzk@kernel.org \
--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
all inboxes | Powered by JetHome®