From: Christopher Li <sparse@chrisli.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Re: error, types differ in signedness
Date: Tue, 6 Feb 2007 10:36:14 -0800 [thread overview]
Message-ID: <20070206183614.GA26248@chrisli.org> (raw)
In-Reply-To: <20070205201255.j8kk0w80gsggo4oo@webmail.spamcop.net>
On Mon, Feb 05, 2007 at 08:12:55PM -0500, Pavel Roskin wrote:
>
> I see. I thought it was easy. Then your patch is fine for me. It's better to
> have no warning than a misleading warning about a stylistic issue.
Sparse care about type difference. What you are asking is not difference
in type. It is the difference in which path it took to reach that type.
E.g. using default degenerating rules or typedefs. Sparse does not
store that information.
Chris
prev parent reply other threads:[~2007-02-06 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 18:54 error, types differ in signedness Randy Dunlap
2007-02-05 20:06 ` [PATCH] " 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 [this message]
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=20070206183614.GA26248@chrisli.org \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@gnu.org \
--cc=rdunlap@xenotime.net \
/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).