From: Joe Perches <joe@perches.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: checkpatch: length of git commit IDs
Date: Sun, 01 Feb 2015 23:30:04 -0800 [thread overview]
Message-ID: <1422862204.30476.1.camel@perches.com> (raw)
In-Reply-To: <20150202082405.6d7d0003@kant>
On Mon, 2015-02-02 at 08:24 +0100, Stefan Richter wrote:
> On Feb 01 Joe Perches wrote:
> > On Sun, 2015-02-01 at 21:30 +0100, Stefan Richter wrote:
> > > On Feb 01 Joe Perches wrote:
> > > > On Sun, 2015-02-01 at 20:59 +0100, Stefan Richter wrote:
> > > > > > ERROR: Please use 12 or more chars for the git commit ID like: 'Commit
> > > > > > 01234567890ab ("commit description")' #5:
> > > > > > Commit 2a48fc0ab242 "block: autoconvert trivial BKL users to private
> [...]
> > > Thanks for the tip; this works for me. (checkpatch.pl from current -next
> > > does actually not complain about the line without parentheses.)
> >
> > Hmm, I think that should be a defect.
> >
> > Can you send me your git format-patch output please?
>
> First of all to be sure: The checkpatch.pl which I last referred to is
> 158501 bytes in size, and the md5sum is bf953e10cbd7405bcf3e885b24c832bd.
> $ scripts/checkpatch.pl patches/scsi-sr-fix-multi-drive-performance-remove-bkl-replacement.patch
> total: 0 errors, 0 warnings, 71 lines checked
Thanks.
I think I "fixed" it with this patch:
https://lkml.org/lkml/2015/2/1/249
next prev parent reply other threads:[~2015-02-02 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 19:59 checkpatch: length of git commit IDs Stefan Richter
2015-02-01 20:09 ` Joe Perches
2015-02-01 20:30 ` Stefan Richter
2015-02-01 20:35 ` Joe Perches
2015-02-02 7:24 ` Stefan Richter
2015-02-02 7:30 ` Joe Perches [this message]
2015-02-02 8:21 ` Stefan Richter
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=1422862204.30476.1.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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