From: Avi Kivity <avi@qumranet.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andy Whitcroft <apw@shadowen.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: latest checkpatch
Date: Thu, 18 Oct 2007 22:02:24 +0200 [thread overview]
Message-ID: <4717BBD0.7070504@qumranet.com> (raw)
In-Reply-To: <20071018193929.GA22031@elte.hu>
Ingo Molnar wrote:
> * Andy Whitcroft <apw@shadowen.org> wrote:
>
>
>>> it's perfectly legitimate, in fact more robust. So if checkpatch.pl
>>> wants to make any noise about such constructs it should warn about
>>> the _lack_ of curly braces in every multi-line condition block
>>> _except_ the only safe single-line statement:
>>>
>>> if (x)
>>> y();
>>>
>> Indeed. We should probabally do more on the indentation checks in
>> general. The current direct check for:
>>
>> if (foo);
>> bar();
>>
>> Could probabally be generalised to look for this kind of error:
>>
>> if (foo)
>> bar();
>> baz();
>> one();
>>
>
> detecting that would be awesome - it's often the sign of a real bug
> because the intent is often to have bar() and baz() in the conditional
> block.
>
>
This is more useful operating on an entire file, so the script can see
all the context.
A 'gcc -Windentation-contradicts-codeflow -Werror' would be nice.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2007-10-18 20:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 19:26 [PATCH] checkpatch: Fix line number reporting Mike D. Day
2007-10-12 19:37 ` Andy Whitcroft
2007-10-13 18:35 ` Erez Zadok
2007-10-15 18:21 ` Andy Whitcroft
2007-10-16 17:59 ` Erez Zadok
2007-10-17 16:39 ` Andy Whitcroft
2007-10-18 11:13 ` latest checkpatch Ingo Molnar
2007-10-18 19:25 ` Andy Whitcroft
2007-10-18 19:39 ` Ingo Molnar
2007-10-18 20:02 ` Avi Kivity [this message]
2007-10-18 20:51 ` Ingo Molnar
2007-10-18 20:57 ` Jeff Garzik
2007-10-18 22:25 ` Randy Dunlap
2007-10-19 9:01 ` Andy Whitcroft
2007-10-18 23:16 ` Andi Kleen
2007-10-19 9:12 ` Ilpo Järvinen
2007-10-18 19:43 ` Andy Whitcroft
2007-10-18 20:00 ` Ingo Molnar
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=4717BBD0.7070504@qumranet.com \
--to=avi@qumranet.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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