From: Al Viro <viro@ftp.linux.org.uk>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-sparse <linux-sparse@vger.kernel.org>,
Michael Wu <flamingice@sourmilk.net>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: sparse missing bitwise warnings with dubious bitfields
Date: Fri, 8 Jun 2007 14:19:09 +0100 [thread overview]
Message-ID: <20070608131909.GZ4095@ftp.linux.org.uk> (raw)
In-Reply-To: <1181291050.6533.19.camel@johannes.berg>
On Fri, Jun 08, 2007 at 10:24:10AM +0200, Johannes Berg wrote:
> $ sparse test.c -DDUBIOUS
> test.c:3:10: error: dubious one-bit signed bitfield
>
> [note that no warning about the bitwise error is there!]
... or any other warnings, for that matter.
Error turns the warnings off.
prev parent reply other threads:[~2007-06-08 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 8:24 sparse missing bitwise warnings with dubious bitfields Johannes Berg
2007-06-08 13:19 ` Al Viro [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=20070608131909.GZ4095@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=flamingice@sourmilk.net \
--cc=hch@infradead.org \
--cc=johannes@sipsolutions.net \
--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