mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Dwaipayan Ray <dwaipayanray1@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
	lukas.bulwahn@gmail.com,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] checkpatch: add new warnings to author signoff checks.
Date: Mon, 05 Oct 2020 11:23:28 -0700	[thread overview]
Message-ID: <14c9d8808feabe987e7fdac867d21ff88561011a.camel@perches.com> (raw)
In-Reply-To: <20201005173933.171074-1-dwaipayanray1@gmail.com>

On Mon, 2020-10-05 at 23:09 +0530, Dwaipayan Ray wrote:
> The author signed-off-by checks are currently very vague.
> Cases like same name or same address are not handled separately.
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> +						if ($address1 =~ /(\S+)\+\S+(\@.*)/) {
> +							$address1 = $1.$2;

More common in this code is "$1" . "$2" not $1.$2

> @@ -6891,9 +6917,29 @@ sub process {
[]
> +			# 4 -> names match, addresses excuding mail extensions (subaddresses) match

excluding

perhaps "subaddress detail" instead of "mail extensions (subaddresses)"

And maybe add "from RFC 5233"

> +
> +			my $sob_msg = "'From: $author' != 'Signed-off-by: $author_sob'";
> +
> +			if ($authorsignoff == 0) {
> +				WARN("NO_AUTHOR_SIGN_OFF",
> +				     "Missing Signed-off-by: line by nominal patch author '$author'\n");
> +			} elsif ($authorsignoff == 2) {
> +				WARN("NO_AUTHOR_SIGN_OFF",
> +				     "From:/Signed-off-by: email name mismatch:\n$sob_msg\n");


Still no need for a newline to separate the output message.



  reply	other threads:[~2020-10-05 18:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 17:39 Dwaipayan Ray
2020-10-05 18:23 ` Joe Perches [this message]
2020-10-05 18:46   ` Dwaipayan Ray
2020-10-05 18:51     ` Joe Perches

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=14c9d8808feabe987e7fdac867d21ff88561011a.camel@perches.com \
    --to=joe@perches.com \
    --cc=dwaipayanray1@gmail.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --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®