From: Bernd Petrovitsch <bernd@firmix.at>
To: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] kmemcheck: fix sparse warning
Date: Thu, 09 Jul 2009 11:48:10 +0200 [thread overview]
Message-ID: <1247132890.25570.3.camel@spike.firmix.at> (raw)
In-Reply-To: <20090709062906.GA14804@feather>
[ stripped people from To: and Cc: - far too trivial and well-known
answer ]
On Wed, 2009-07-08 at 23:29 -0700, Josh Triplett wrote:
> [Adding Linus and Chris Li to CC; Linus for further background on
> -Wdo-while, and Chris Li for Sparse.]
[....]
> Much discussion has occurred previously suggesting that Sparse's -Wall
> should match GCC's "all useful warnings" rather than "all possible
this is usually phrased as "all useful warnings in RMS opinion". I'm not
sure how far RMS influence is today on that.
> warnings", and some other option should exist for "all possible
> warnings" (for instance, -Weverything). This seems very reasonable.
gcc's has "-Wextra" since ages which enables lots of other (IMHO) useful
warnings.
But it's just a name ....
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
prev parent reply other threads:[~2009-07-09 9:54 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
2009-07-09 9:48 ` Bernd Petrovitsch [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=1247132890.25570.3.camel@spike.firmix.at \
--to=bernd@firmix.at \
--cc=linux-sparse@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