From: Andy Whitcroft <apw@shadowen.org>
To: penguin-kernel@i-love.sakura.ne.jp
Cc: rdunlap@xenotime.net, jschopp@austin.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: */ in string confuses checkpatch.pl
Date: Wed, 22 Oct 2008 09:31:41 +0100 [thread overview]
Message-ID: <20081022083141.GB22344@brain> (raw)
In-Reply-To: <20081022075617.GA22344@brain>
On Wed, Oct 22, 2008 at 08:56:17AM +0100, Andy Whitcroft wrote:
> On Tue, Oct 21, 2008 at 09:57:26AM +0900, penguin-kernel@i-love.sakura.ne.jp wrote:
> > Hello.
> >
> > The below code confuses checkpatch.pl ver 0.21.
> >
> > Regards.
> > ----------
> > # cat /tmp/foo.c
> > void foo(void)
> > {
> > bar(\" /proc/\\\\*/\");
> > bar(\" /proc/\\\\$/\");
> > }
> > # /usr/src/vanilla/linux-2.6.27.2/scripts/checkpatch.pl --file /tmp/foo.c
> > ERROR: need consistent spacing around \'/\' (ctx:WxV)
> > #4: FILE: tmp/foo.c:4:
> > + bar(\" /proc/\\\\$/\");
> > ^
> >
> > total: 1 errors, 0 warnings, 5 lines checked
> >
> > /tmp/foo.c has style problems, please review. If any of these errors
> > are false positives report them to the maintainer, see
> > CHECKPATCH in MAINTAINERS.
Ok, I can see whats happened here. Most of these \'s are extraneous.
Without those I can reproduce this. Its a bug in the 'comment is open
at the start of hunk' detection. I think I have updated this heuristic
to cope wit this. Could you try your original patch (I assume there was
one) with the version below:
http://www.kernel.org/pub/linux/kernel/people/apw/checkpatch/checkpatch.pl-testing
Thanks for your report.
-apw
next prev parent reply other threads:[~2008-10-22 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 0:57 */ in string confuses checkpatch.pl penguin-kernel
2008-10-22 7:56 ` Andy Whitcroft
2008-10-22 8:02 ` Tetsuo Handa
2008-10-22 8:31 ` Andy Whitcroft [this message]
2008-10-22 11:21 ` Tetsuo Handa
2008-10-23 11:27 ` [checkpatch.pl] two bugs Tetsuo Handa
2008-10-23 11:54 ` Andy Whitcroft
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=20081022083141.GB22344@brain \
--to=apw@shadowen.org \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rdunlap@xenotime.net \
/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