From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: netdev@vger.kernel.org
Subject: Re: sparse noise due to patch "net: fix kmemcheck annotations"
Date: Wed, 11 Nov 2009 22:13:02 +0100 [thread overview]
Message-ID: <4AFB28DE.8070000@gmail.com> (raw)
In-Reply-To: <4AFB217E.2040209@s5r6.in-berlin.de>
Stefan Richter a écrit :
> Hi Eric,
>
> with above mentioned patch, committed as
> 14d18a81b5171d4433e41129619c75748b4f4d26, you changed
>
> struct sk_buff {
> ...
> __be16 protocol;
> ...
> }
> to
> __be16 protocol:16;
>
> This introduces the following warning from sparse:
>
> include/linux/skbuff.h:357:41: error: invalid bitfield specifier for
> type restricted __be16.
>
> So, one checker satisfied, another disturbed? Any idea how to get this
> sparse-clean again?
No problem here... how do you get this error, and what is your sparse version ?
next prev parent reply other threads:[~2009-11-11 21:13 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 [this message]
2009-11-11 21:42 ` Stefan Richter
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=4AFB28DE.8070000@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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).