From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: sparse noise due to patch "net: fix kmemcheck annotations"
Date: Wed, 11 Nov 2009 22:42:40 +0100 [thread overview]
Message-ID: <4AFB2FD0.4070805@s5r6.in-berlin.de> (raw)
In-Reply-To: <4AFB28DE.8070000@gmail.com>
Eric Dumazet wrote:
> Stefan Richter a écrit :
>> include/linux/skbuff.h:357:41: error: invalid bitfield specifier for
>> type restricted __be16.
...
> No problem here... how do you get this error, and what is your sparse version ?
It's sparse 0.4.2.
The note is only logged with 'make ... CF="-D__CHECK_ENDIAN__"'.
I guess sparse could be taught to ignore :_ suffixes if the suffix
covers the whole width of the type... unless there is something that
could be improved in kmemcheck.
--
Stefan Richter
-=====-==--= =-== -=-==
http://arcgraph.de/sr/
prev parent reply other threads:[~2009-11-11 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 20:41 sparse noise due to patch "net: fix kmemcheck annotations" Stefan Richter
2009-11-11 21:13 ` Eric Dumazet
2009-11-11 21:42 ` Stefan Richter [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=4AFB2FD0.4070805@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=eric.dumazet@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).