From: Fengguang Wu <fengguang.wu@intel.com>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org
Subject: [net-next:master 126/134] include/net/ipv6.h:555:26: sparse: cast to restricted __be32
Date: Mon, 14 Jan 2013 10:55:59 +0800 [thread overview]
Message-ID: <20130114025559.GA9331@localhost> (raw)
In-Reply-To: <50f370b4.sImtI783JLS2vUID%yuanhan.liu@linux.intel.com>
Hi YOSHIFUJI,
FYI, there are new sparse warnings show up in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head: 25d46f43a911b08c5aa8c8fd4fe7fa9b36445068
commit: 3e4e4c1f2da66b29ee9379ca29f8dd620c2b5a1f [126/134] ipv6: Introduce ip6_flow_hdr() to fill version, tclass and flowlabel.
>> include/net/ipv6.h:555:26: sparse: cast to restricted __be32
>> include/net/ipv6.h:555:63: sparse: restricted __be32 degrades to integer
>> include/net/ipv6.h:555:24: sparse: incorrect type in assignment (different base types)
include/net/ipv6.h:555:24: expected restricted __be32 [usertype] <noident>
include/net/ipv6.h:555:24: got unsigned int
vim +555 include/net/ipv6.h
971f359d YOSHIFUJI Hideaki 2005-11-08 549 /*
3e4e4c1f YOSHIFUJI Hideaki / 吉藤英明 2013-01-13 550 * Header manipulation
3e4e4c1f YOSHIFUJI Hideaki / 吉藤英明 2013-01-13 551 */
3e4e4c1f YOSHIFUJI Hideaki / 吉藤英明 2013-01-13 552 static inline void ip6_flow_hdr(struct ipv6hdr *hdr, unsigned int tclass,
3e4e4c1f YOSHIFUJI Hideaki / 吉藤英明 2013-01-13 553 __be32 flowlabel)
3e4e4c1f YOSHIFUJI Hideaki / 吉藤英明 2013-01-13 554 {
3e4e4c1f YOSHIFUJI Hideaki / 吉藤英明 2013-01-13 @555 *(__be32 *)hdr = ntohl(0x60000000 | (tclass << 20)) | flowlabel;
3e4e4c1f YOSHIFUJI Hideaki / 吉藤英明 2013-01-13 556 }
3e4e4c1f YOSHIFUJI Hideaki / 吉藤英明 2013-01-13 557
3e4e4c1f YOSHIFUJI Hideaki / 吉藤英明 2013-01-13 558 /*
---
0-DAY kernel build testing backend Open Source Technology Center
Fengguang Wu, Yuanhan Liu Intel Corporation
parent reply other threads:[~2013-01-14 2:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <50f370b4.sImtI783JLS2vUID%yuanhan.liu@linux.intel.com>]
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=20130114025559.GA9331@localhost \
--to=fengguang.wu@intel.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.