From: Andy Whitcroft <apw@canonical.com>
To: Joe Perches <joe@perches.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Possible false positive from checkpatch.pl
Date: Wed, 14 Jul 2010 14:14:47 +0100 [thread overview]
Message-ID: <20100714131447.GC20746@shadowen.org> (raw)
In-Reply-To: <1278964147.1501.291.camel@Joe-Laptop.home>
On Mon, Jul 12, 2010 at 12:49:07PM -0700, Joe Perches wrote:
> On Mon, 2010-07-12 at 14:37 -0500, Larry Finger wrote:
> > On 07/12/2010 02:03 PM, Joe Perches wrote:
> > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > > index bd88f11..7e8a3f4 100755
> > > --- a/scripts/checkpatch.pl
> > > +++ b/scripts/checkpatch.pl
> > > @@ -2394,8 +2394,10 @@ sub process {
> > > }x;
> > > #print "REST<$rest> dstat<$dstat>\n";
> > > if ($rest ne '') {
> > > - if ($rest !~ /while\s*\(/&&
> > > - $dstat !~ /$exceptions/)
> > > + if ($rest eq ",") {
> > > + ERROR("Macros should not end with a trailing comma\n" . "$here\n$ctx\n");
> > > + } elsif ($rest !~ /while\s*\(/&&
> > > + $dstat !~ /$exceptions/)
> > > {
> > > ERROR("Macros with multiple statements should be enclosed in a do - while loop\n" . "$here\n$ctx\n");
> > > }
> >
> > That looks good. At least it makes clear what is wrong.
> > Should it be an error, or just a warning?
>
> I don't much care.
>
> If Andy wants to do anything, let him decide.
>
> Perhaps the new test should be
> if ($rest =~ /\s*,\s*$/)
I am not sure these are even invalid are they? Macro abuse of this sort
is always going to throw up exceptions. Hrmm.
-apw
next prev parent reply other threads:[~2010-07-14 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 17:52 Larry Finger
2010-07-12 18:28 ` Joe Perches
2010-07-12 18:35 ` Larry Finger
2010-07-12 19:03 ` Joe Perches
2010-07-12 19:37 ` Larry Finger
2010-07-12 19:49 ` Joe Perches
2010-07-14 13:14 ` Andy Whitcroft [this message]
2010-07-14 16:16 ` Joe Perches
2010-07-14 13:13 ` 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=20100714131447.GC20746@shadowen.org \
--to=apw@canonical.com \
--cc=Larry.Finger@lwfinger.net \
--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 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®