From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
Cc: gregkh@linuxfoundation.org, himanshujha199640@gmail.com,
apw@canonical.com, linux-kernel@vger.kernel.org,
niklas.cassel@linaro.org, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] checkpatch: add Co-developed-by to signature tags
Date: Sat, 15 Dec 2018 09:45:00 -0800 [thread overview]
Message-ID: <9d20d06ea2b92e6b66f0a2dc58f8b191fd7778ce.camel@perches.com> (raw)
In-Reply-To: <20181214121634.1157f2302c8ba1825fc03ad2@linux-foundation.org>
On Fri, 2018-12-14 at 12:16 -0800, Andrew Morton wrote:
> On Fri, 14 Dec 2018 18:35:28 +0100 Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org> wrote:
>
> > As per Documentation/process/submitting-patches, Co-developed-by is a
> > valid signature.
> >
>
> I'm with Joe - I find this tag kinda useless and duplicative. But whatever.
>
> But as the documentation says, Co-developed-by must be accompanied by a
> Signed-off-by:. It would be helpful if checkpatch were to detect a
> failure to do this.
perhaps
---
scripts/checkpatch.pl | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 93e84c9504a1..056d4b47ffaf 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2673,7 +2673,20 @@ sub process {
WARN("BAD_SIGN_OFF",
"Duplicate signature\n" . $herecurr);
} else {
- $signatures{$sig_nospace} = 1;
+ $signatures{$sig_nospace} = $herecurr;
+ }
+ }
+
+# Check for "Co-developed-by:" uses without equivalent "Signed-off-by:"
+# $signatures keys are all lower case without spaces
+ if ($rawline =~ /^---$/) {
+ foreach my $sig (keys %signatures) {
+ next if ($sig !~ /^co-developed-by:(.*)/);
+ my $signer = $1;
+ if (!defined $signatures{"signed-off-by:$signer"}) {
+ WARN("CODEVELOPED_WITHOUT_SIGNOFF",
+ "Co-developed-by: used without Signed-off-by: by same person\n" . $signatures{$sig});
+ }
}
}
prev parent reply other threads:[~2018-12-15 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 17:35 [PATCH 0/2] Fix Co-Developed-by Jorge Ramirez-Ortiz
2018-12-14 17:35 ` [PATCH 1/2] docs: fix Co-Developed-by docs Jorge Ramirez-Ortiz
2018-12-14 18:12 ` Himanshu Jha
2018-12-14 17:35 ` [PATCH 2/2] checkpatch: add Co-developed-by to signature tags Jorge Ramirez-Ortiz
2018-12-14 20:16 ` Andrew Morton
2018-12-14 20:58 ` Himanshu Jha
2018-12-15 17:45 ` Joe Perches [this message]
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=9d20d06ea2b92e6b66f0a2dc58f8b191fd7778ce.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=himanshujha199640@gmail.com \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niklas.cassel@linaro.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;
as well as URLs for NNTP newsgroup(s).