From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Douglas Anderson <dianders@chromium.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
Jason Wessel <jason.wessel@windriver.com>,
Christophe Leroy <christophe.leroy@c-s.fr>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Kees Cook <keescook@chromium.org>,
kgdb-bugreport@lists.sourceforge.net,
Johannes Weiner <hannes@cmpxchg.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Nicholas Mc Guire <hofrat@osadl.org>
Subject: Re: [PATCH] kdb: Get rid of broken attempt to print CCVERSION in kdb summary
Date: Fri, 19 Apr 2019 13:58:30 -0700 [thread overview]
Message-ID: <20190419135830.0e3273e223fb83947e5adb0d@linux-foundation.org> (raw)
In-Reply-To: <e5f29ca9b6067fff9ea68cb25e15906659cd51ad.camel@perches.com>
On Fri, 19 Apr 2019 04:14:27 -0700 Joe Perches <joe@perches.com> wrote:
> On Fri, 2019-04-19 at 12:28 +0900, Masahiro Yamada wrote:
> > Hi Joe,
> >
> > Can you detect redundant Cc: by checkpatch?
> >
> > Please see below in details.
> > Thanks.
>
> Yes, but I'm not sure why it's useful or necessary.
> git send-email using some scripts elides duplicate email addresses
Other (all?) MUAs will avoid addressing an email to a recipient more
than once. The issue here is redundant Cc: lines in the changelog.
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2688,6 +2688,19 @@ sub process {
> $signatures{$sig_nospace} = 1;
> }
>
> +# Check for a cc: line with another signature -by: by the same author
> + if ($sig_nospace =~ /^cc:/) {
> + my $sig_email = substr($sig_nospace, 3);
> + foreach my $sig (sort keys %signatures) {
> + next if ($sig =~ /^cc:/);
> + $sig =~ s/^[^:]+://;
> + if ($sig eq $sig_email) {
> + WARN("BAD_SIGN_OFF",
> + "Unnecessary CC: as there is another signature with the same name/email address\n" . $herecurr);
> + }
> + }
> + }
> +
> # Check Co-developed-by: immediately followed by Signed-off-by: with same name and email
> if ($sign_off =~ /^co-developed-by:$/i) {
> if ($email eq $author) {
Thanks. But my checkpatch.pl is different from yours.
q:/usr/src/25> grep "immediately followed by" scripts/checkpatch.pl
q:/usr/src/25>
next prev parent reply other threads:[~2019-04-19 20:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 1:52 Douglas Anderson
2019-03-30 12:14 ` Masahiro Yamada
2019-04-11 9:06 ` Masahiro Yamada
2019-04-16 23:30 ` Andrew Morton
2019-04-17 6:37 ` Masahiro Yamada
2019-04-18 23:06 ` Andrew Morton
2019-04-19 3:28 ` Masahiro Yamada
2019-04-19 11:14 ` Joe Perches
2019-04-19 20:58 ` Andrew Morton [this message]
2019-04-20 3:57 ` Joe Perches
2019-05-06 14:28 ` Masahiro Yamada
2019-05-07 13:55 ` Daniel Thompson
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=20190419135830.0e3273e223fb83947e5adb0d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=christophe.leroy@c-s.fr \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=gustavo@embeddedor.com \
--cc=hannes@cmpxchg.org \
--cc=hofrat@osadl.org \
--cc=jason.wessel@windriver.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=yamada.masahiro@socionext.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®