From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-sparse@vger.kernel.org
Subject: error, types differ in signedness
Date: Mon, 5 Feb 2007 10:54:20 -0800 [thread overview]
Message-ID: <20070205105420.6f19a57d.rdunlap@xenotime.net> (raw)
Hi,
On Linux 2.6.20 and current sparse, I see these warnings:
net/core/skbuff.c:1838:5: error: symbol 'skb_append_datato_frags' redeclared with different type (originally declared at include/linux/skbuff.h:380) - incompatible argument 3 (different signedness)
fs/mpage.c:821:5: error: symbol 'mpage_writepage' redeclared with different type (originally declared at include/linux/mpage.h:22) - incompatible argument 2 (different signedness)
These are both in function pointers that are arguments to a function.
The skbuff.[hc] difference is in *getfrag vs. getfrag.
The mpage.[hc] difference is in *get_block vs. getblock.
Questions:
1. Is the warning valid?
2. Isn't the '*' unnecessary?
Thanks,
---
~Randy
next reply other threads:[~2007-02-05 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 18:54 Randy Dunlap [this message]
2007-02-05 20:06 ` [PATCH] Re: error, types differ in signedness Christopher Li
2007-02-05 21:04 ` Randy Dunlap
2007-02-05 22:27 ` Pavel Roskin
2007-02-06 0:16 ` Christopher Li
2007-02-06 1:12 ` Pavel Roskin
2007-02-06 18:36 ` Christopher Li
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=20070205105420.6f19a57d.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-sparse@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).