From: Joe Perches <joe@perches.com>
To: Changbin Du <changbin.du@gmail.com>, Andy Whitcroft <apw@canonical.com>
Cc: linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] checkpatch: warn on bad commit description in 'Fixes' tag
Date: Tue, 19 Feb 2019 01:22:06 -0800 [thread overview]
Message-ID: <0cc49d981dac5a51d9810b58b95ea8ccf82f3a7b.camel@perches.com> (raw)
In-Reply-To: <20190219063611.19955-1-changbin.du@gmail.com>
On Tue, 2019-02-19 at 06:36 +0000, Changbin Du wrote:
> There are some complaints about bad commit description in 'Fixes' tag.
> Most cases are SHA1 should be at least 12 digits long. Let's extend
> the existing check in checkpatch.pl to include commit description of
> 'Fixes' tag.
I sent a suggested patch a bit ago
https://lore.kernel.org/lkml/40bfc40958fca6e2cc9b86101153aa0715fac4f7.camel@perches.com/
prev parent reply other threads:[~2019-02-19 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 6:36 Changbin Du
2019-02-19 9:22 ` 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=0cc49d981dac5a51d9810b58b95ea8ccf82f3a7b.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=changbin.du@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®