From: Hannes Eder <hannes@hanneseder.net>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Linux Torvalds <torvalds@linux-foundation.org>,
Johannes Berg <johannes@sipsolutions.net>,
Pekka J Enberg <penberg@cs.helsinki.fi>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH] kmemcheck: fix sparse warning
Date: Thu, 9 Jul 2009 09:00:02 +0200 [thread overview]
Message-ID: <154e089b0907090000r54dc2436ta25b58395a04acc@mail.gmail.com> (raw)
In-Reply-To: <20090709062906.GA14804@feather>
On Thu, Jul 9, 2009 at 08:29, Josh Triplett<josh@joshtriplett.org> wrote:
> [Adding Linus and Chris Li to CC; Linus for further background on
> -Wdo-while, and Chris Li for Sparse.]
>
> On Wed, Jul 08, 2009 at 09:28:24PM +0200, Vegard Nossum wrote:
>> 2009/7/6 Johannes Berg <johannes@sipsolutions.net>:
>> > Whether or not the sparse warning
>> >
>> > warning: do-while statement is not a compound statement
>> >
>> > is justified or not in this case, it is annoying and
>> > trivial to fix.
> [...]
>>
>> I'll change the patch title to "kmemcheck: work around bogus sparse
>> warning" and fix the indentation, sounds ok?
>>
>> Meanwhile, I Cced sparse mailing list in case somebody else knows
>> anything else about this warning (what it means, whether it's
>> justified in this case, whether it should be fixed in sparse, etc.).
>
> -Wdo-while gives a warning if you write:
>
> do
> statement
> while (...);
>
> where "statement" does not consist of a compound statement surrounded by
> braces. As far as I know, this warning exists primarily because it
> matched Linus's preference for readability.
see:
http://lkml.org/lkml/2008/12/23/180
an related messages/threads
Cheers,
-Hannes
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-07-09 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1246873983.20908.0.camel@johannes.local>
2009-07-08 19:28 ` [PATCH] kmemcheck: fix sparse warning Vegard Nossum
2009-07-08 19:39 ` Johannes Berg
2009-07-08 20:28 ` Christopher Li
2009-07-09 6:29 ` Josh Triplett
2009-07-09 7:00 ` Hannes Eder [this message]
2009-07-09 9:48 ` Bernd Petrovitsch
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=154e089b0907090000r54dc2436ta25b58395a04acc@mail.gmail.com \
--to=hannes@hanneseder.net \
--cc=johannes@sipsolutions.net \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@gmail.com \
/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