From: Joe Perches <joe@perches.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Andy Whitcroft <apw@canonical.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scripts: checkpatch: ignore stable commit annotation
Date: Tue, 30 Jun 2015 15:30:35 -0700 [thread overview]
Message-ID: <1435703435.12101.50.camel@perches.com> (raw)
In-Reply-To: <1435702063-12871-1-git-send-email-balbi@ti.com>
On Tue, 2015-06-30 at 17:07 -0500, Felipe Balbi wrote:
> When running scripts/checkpatch.pl on stable commits,
> we always get the error for not using 12-character
> commit hash abbreviation with shortlog within ("").
Looking at linux-stable v3.14.44 (randomly chosen), there
are also commit entries like:
This is commit 0f540c3a7cfb91c9d7a19eb0c95c24 upstream.
commit: cb64edb6b89491edfdbae52ba7db9a8b8391d339 upstream
is -stable now using some script to tag these or is it
freehanded and happens to be reasonably consistent?
> Because that's actually a false positive, let's ignore
> stable commit annotation.
This will have to be respun against another patch:
https://lkml.org/lkml/2015/6/19/491
Please cc Andrew Morton if you resubmit.
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -2330,6 +2331,7 @@ sub process {
> my $orig_desc = "commit description";
> my $description = "";
>
> + $stable = 1 if ($line =~ /\bcommit\s+[0-9a-f]{40}\s+upstream\./i);
If these are really scripted, the case-insensitive /i
shouldn't be necessary.
next prev parent reply other threads:[~2015-06-30 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 22:07 [PATCH] scripts: checkpatch: ignore stable commit annotation Felipe Balbi
2015-06-30 22:30 ` Joe Perches [this message]
2015-06-30 22:42 ` Felipe Balbi
2015-06-30 23:45 ` Greg KH
2015-07-01 0:53 ` Felipe Balbi
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=1435703435.12101.50.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=balbi@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox