From: Joe Perches <joe@perches.com>
To: Gregory Fong <gregory.0xf0@gmail.com>
Cc: Andy Whitcroft <apw@canonical.com>,
Brian Norris <computersforpeace@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] checkpatch.pl: 1-tab relative indent for conditionals/blocks
Date: Fri, 18 Jul 2014 13:39:32 -0700 [thread overview]
Message-ID: <1405715972.14358.81.camel@joe-AO725> (raw)
In-Reply-To: <1405712447-18788-1-git-send-email-gregory.0xf0@gmail.com>
On Fri, 2014-07-18 at 12:40 -0700, Gregory Fong wrote:
> The following would incorrectly pass checkpatch:
>
> void foo(void)
> {
> if (a) {
> something;
> somethingelse;
> } else {
> messed_up_indentation;
> }
> }
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -2606,6 +2607,7 @@ sub process {
> #print "line<$line> prevline<$prevline> indent<$indent> sindent<$sindent> check<$check> continuation<$continuation> s<$s> cond_lines<$cond_lines> stat_real<$stat_real> stat<$stat>\n";
>
> if ($check && (($sindent % 8) != 0 ||
> + ((($sindent - $indent) / 8) > 1) ||
> ($sindent <= $indent && $s ne ''))) {
> WARN("SUSPECT_CODE_INDENT",
> "suspect code indent for conditional statements ($indent, $sindent)\n" . $herecurr . "$stat_real\n");
This might be better testing only tab indented lines like:
if ($check &&
length($prevtabindent) + 1 != length($tabindent))
It'd also be useful to check non-conditional, non-blank
after decommenting code lines so that a block like:
static bool func(void)
{
bool b;
/* comment about something */
int a[2] = foo();
b = a[0] == a[1];
/* ready to return */
return b;
}
emits a couple of "suspect code indent" warnings.
One on int a[2], another on return b.
prev parent reply other threads:[~2014-07-18 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 19:40 [PATCH 1/1] checkpatch.pl: 1-tab relative indent for conditionals/blocks Gregory Fong
2014-07-18 20:39 ` 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=1405715972.14358.81.camel@joe-AO725 \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=computersforpeace@gmail.com \
--cc=gregory.0xf0@gmail.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