From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [nf-next:mmap-netlink 61/68] net/netlink/af_netlink.c:194:39: sparse: incorrect type in return expre
Date: Thu, 12 Jul 2012 23:46:00 +0000 [thread overview]
Message-ID: <20120712234600.GB5608@localhost> (raw)
Hi Patrick,
There are new sparse warnings show up in
tree: git://150.214.188.80/nf-next mmap-netlink
head: c7e7243d0b69e2323dde057c28f1102d00e5a3c6
commit: a20a76bdf79a4b6c25df3ad1a48fd601a0b59400 [61/68] netlink: mmaped netlink: ring setup
All sparse warnings:
+ net/netlink/af_netlink.c:194:39: sparse: incorrect type in return expression (different modifiers)
net/netlink/af_netlink.c:194:39: expected struct page [pure] *
net/netlink/af_netlink.c:194:39: got struct page *
net/netlink/af_netlink.c:196:24: sparse: incorrect type in return expression (different modifiers)
net/netlink/af_netlink.c:196:24: expected struct page [pure] *
net/netlink/af_netlink.c:196:24: got struct page *
+ net/netlink/af_netlink.c:397:38: sparse: incorrect type in assignment (different modifiers)
net/netlink/af_netlink.c:397:38: expected struct page *page
net/netlink/af_netlink.c:397:38: got struct page [pure] *
net/netlink/af_netlink.c:819:56: sparse: incorrect type in argument 1 (different address spaces)
net/netlink/af_netlink.c:819:56: expected void const *<noident>
net/netlink/af_netlink.c:819:56: got struct listeners [noderef] <asn:4>*listeners
net/netlink/af_netlink.c:632:38: sparse: dereference of noderef expression
vim +194 net/netlink/af_netlink.c
191 static __pure struct page *pgvec_to_page(const void *addr)
192 {
193 if (is_vmalloc_addr(addr))
> 194 return vmalloc_to_page(addr);
195 else
196 return virt_to_page(addr);
197 }
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
reply other threads:[~2012-07-12 23:46 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=20120712234600.GB5608@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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).