All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] checkpatch: require Fixes tag for fixup patches
Date: Tue, 11 Jan 2022 14:47:36 +0900	[thread overview]
Message-ID: <Yd0Z+MoYHExGaKCL@google.com> (raw)
In-Reply-To: <20211130111503.2930770-1-senozhatsky@chromium.org>

On (21/11/30 20:15), Sergey Senozhatsky wrote:
> 
> Require "Fixes: hash" tag in those patches that appear to be
> fixing some particular commit.

Gentle ping.

> Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
> ---
>  scripts/checkpatch.pl | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)
> 
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index df8b23dc1eb0..4e97d0f6b995 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2493,6 +2493,9 @@ sub process {
>  	my $commit_log_has_diff = 0;
>  	my $reported_maintainer_file = 0;
>  	my $non_utf8_charset = 0;
> +	my $fixes_id = 0;
> +	my $fixes_description = 0;
> +	my $fixes_tag = 0;
>  
>  	my $last_blank_line = 0;
>  	my $last_coalesced_string_linenr = -1;
> @@ -3076,6 +3079,11 @@ sub process {
>  			}
>  		}
>  
> +# Check for Fixes tag
> +		if ($in_commit_log && $line =~ /\b[Ff]ixes:\s*[0-9a-f]{12,40}/) {
> +			$fixes_tag = 1;
> +		}
> +
>  # Check for git id commit length and improperly formed commit descriptions
>  		if ($in_commit_log && !$commit_log_possible_stack_dump &&
>  		    $line !~ /^\s*(?:Link|Patchwork|http|https|BugLink|base-commit):/i &&
> @@ -3128,6 +3136,11 @@ sub process {
>  			($id, $description) = git_commit_info($orig_commit,
>  							      $id, $orig_desc);
>  
> +			if (defined($id)) {
> +				$fixes_id = $id;
> +				$fixes_description = $description;
> +			}
> +
>  			if (defined($id) &&
>  			   ($short || $long || $space || $case || ($orig_desc ne $description) || !$hasparens)) {
>  				ERROR("GIT_COMMIT_ID",
> @@ -7326,6 +7339,12 @@ sub process {
>  		}
>  	}
>  
> +	if ($is_patch && $has_commit_log && $fixes_id && !$fixes_tag) {
> +		ERROR("GIT_COMMIT_ID",
> +		      "Please add 'Fixes: $fixes_id (\"$fixes_description\")'\n", );
> +		$fixes_id = 0;
> +	}
> +
>  	print report_dump();
>  	if ($summary && !($clean == 1 && $quiet == 1)) {
>  		print "$filename " if ($summary_file);
> -- 
> 2.34.0.rc2.393.gf8c9666880-goog
> 

      reply	other threads:[~2022-01-11  5:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 11:15 [RFC][PATCH] checkpatch: require Fixes tag for fixup patches Sergey Senozhatsky
2022-01-11  5:47 ` Sergey Senozhatsky [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=Yd0Z+MoYHExGaKCL@google.com \
    --to=senozhatsky@chromium.org \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.