From: Thomas Graf <tgraf@suug.ch>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>, hans.verkuil@cisco.com
Subject: Re: [PATCH] sparse: Fix ioc type check
Date: Thu, 25 Sep 2014 13:30:58 +0100 [thread overview]
Message-ID: <20140925123058.GI4966@casper.infradead.org> (raw)
In-Reply-To: <CANeU7Qkg9zBUoggGLBtFq6_-Svh9C2XHsFKdqvQ3TGaGNMZ79w@mail.gmail.com>
On 09/25/14 at 08:10pm, Christopher Li wrote:
> No, this test case is some thing gcc can handle and sparse
> can't. Instead of patching the test result, we need to fix sparse
> to handle it correctly.
>
> It is an open bug of sparse.
OK. This was not clear from the commit message.
Thanks for clarifying.
prev parent reply other threads:[~2014-09-25 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 8:20 [PATCH] sparse: Fix ioc type check Thomas Graf
2014-09-25 12:10 ` Christopher Li
2014-09-25 12:30 ` Thomas Graf [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=20140925123058.GI4966@casper.infradead.org \
--to=tgraf@suug.ch \
--cc=hans.verkuil@cisco.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).