From: kbuild test robot <lkp@intel.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org
Subject: [net:master 27/28] net/sctp/offload.c:39:33: sparse: warning: incorrect type in argument 2 (different base types)
Date: Thu, 14 Feb 2019 14:31:09 +0800 [thread overview]
Message-ID: <201902141407.shGwbhh6%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git master
head: af98c5a78517c04adb5fd68bb64b1ad6fe3d473f
commit: fc228abc2347e106a44c0e9b29ab70b712c4ca51 [27/28] sctp: call gso_reset_checksum when computing checksum in sctp_gso_segment
reproduce:
# apt-get install sparse
git checkout fc228abc2347e106a44c0e9b29ab70b712c4ca51
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
All warnings (new ones prefixed by >>):
>> net/sctp/offload.c:39:33: sparse: warning: incorrect type in argument 2 (different base types)
net/sctp/offload.c:39:33: sparse: expected restricted __wsum [usertype] res
net/sctp/offload.c:39:33: sparse: got int
sparse warnings: (new ones prefixed by >>)
net/sctp/offload.c:39:33: sparse: warning: incorrect type in argument 2 (different base types)
>> net/sctp/offload.c:39:33: sparse: expected restricted __wsum [usertype] res
>> net/sctp/offload.c:39:33: sparse: got int
vim +39 net/sctp/offload.c
34
35 static __le32 sctp_gso_make_checksum(struct sk_buff *skb)
36 {
37 skb->ip_summed = CHECKSUM_NONE;
38 skb->csum_not_inet = 0;
> 39 gso_reset_checksum(skb, ~0);
40 return sctp_compute_cksum(skb, skb_transport_offset(skb));
41 }
42
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 67238 bytes --]
reply other threads:[~2019-02-14 6:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201902141407.shGwbhh6%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=lucien.xin@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