From: Andy Whitcroft <apw@canonical.com>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: Add for_each tests to indentation and brace tests
Date: Mon, 14 Jul 2014 09:13:52 +0100 [thread overview]
Message-ID: <20140714081352.GE3743@bark> (raw)
In-Reply-To: <1405229634.9132.38.camel@joe-AO725>
On Sat, Jul 12, 2014 at 10:33:54PM -0700, Joe Perches wrote:
> All the various for_each loop macros were not tested for
> trailing brace on the following lines and for bad indentation.
>
> Add them.
>
> Reported-by: Greg KH <gregkh@linuxfoundation.org>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
> On Sat, 2014-07-12 at 16:08 -0700, Greg KH wrote:
> > The following function:
> >
> > $ cat foo.c
> >
> > static int foo_init(void)
> > {
> >
> > list_for_each_entry(foo, &foo, list)
> > {
> > do_something_foo(foo);
> > }
> >
> > return 0;
> > }
> >
> > Will not be caught by checkpatch:
> >
> > $ ./scripts/checkpatch.pl --file foo.c
> > total: 0 errors, 0 warnings, 11 lines checked
> >
> > foo.c has no obvious style problems and is ready for submission.
>
> scripts/checkpatch.pl | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index d5ac001..5efbf50 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2698,7 +2698,7 @@ sub process {
>
> # if/while/etc brace do not go on next line, unless defining a do while loop,
> # or if that brace on the next line is for something else
> - if ($line =~ /(.*)\b((?:if|while|for|switch)\s*\(|do\b|else\b)/ && $line !~ /^.\s*\#/) {
> + if ($line =~ /(.*)\b((?:if|while|for|switch|(?:[a-z_]+|)for_each[a-z_]+)\s*\(|do\b|else\b)/ && $line !~ /^.\s*\#/) {
They way you end this first addition with |) converts it the (?:[a-z_]*)
doesn't it? Were you intending to do (?:[a-z_]+_|) ?
> my $pre_ctx = "$1$2";
>
> my ($level, @ctx) = ctx_statement_level($linenr, $realcnt, 0);
> @@ -2744,7 +2744,7 @@ sub process {
> }
>
> # Check relative indent for conditionals and blocks.
> - if ($line =~ /\b(?:(?:if|while|for)\s*\(|do\b)/ && $line !~ /^.\s*#/ && $line !~ /\}\s*while\s*/) {
> + if ($line =~ /\b(?:(?:if|while|for|(?:[a-z_]+|)for_each[a-z_]+)\s*\(|do\b)/ && $line !~ /^.\s*#/ && $line !~ /\}\s*while\s*/) {
> ($stat, $cond, $line_nr_next, $remain_next, $off_next) =
> ctx_statement_block($linenr, $realcnt, 0)
> if (!defined $stat);
With the above clarified it all seems sensible.
Acked-by: Andy Whitcroft <apw@canonical.com>
-apw
next prev parent reply other threads:[~2014-07-14 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 23:08 checkpatch.pl misses list_for_each_entry() coding style issues Greg KH
2014-07-13 3:10 ` Joe Perches
2014-07-13 5:33 ` [PATCH] checkpatch: Add for_each tests to indentation and brace tests Joe Perches
2014-07-14 8:13 ` Andy Whitcroft [this message]
2014-07-14 8:18 ` Joe Perches
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=20140714081352.GE3743@bark \
--to=apw@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--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
Powered by JetHome