From: Christopher Li <sparse@chrisli.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Bogus 'Initializer entry defined twice' warnings
Date: Wed, 5 Nov 2014 18:49:23 +0800 [thread overview]
Message-ID: <CANeU7QmfgPwOk0LMaUFxaH6UzA03NUizR6ybZ58NGkPEd3OkvQ@mail.gmail.com> (raw)
In-Reply-To: <5459D56E.3080704@xs4all.nl>
On Wed, Nov 5, 2014 at 3:44 PM, Hans Verkuil <hverkuil@xs4all.nl> wrote:
> Ping!
>
> This is still failing (tested with the latest sparse v0.5.0-35-gc1c3f96
> from git://git.kernel.org/pub/scm/devel/sparse/chrisl/sparse.git).
>
> I'd really like to get rid of these spurious sparse warnings.
Sorry I did not know this warning still exist. There have been some
fix for similar
warnings. I just confirm that your example reproduce the warning in my sparse
tree.
I will take a look.
Thanks
Chris
next prev parent reply other threads:[~2014-11-05 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 8:10 Bogus 'Initializer entry defined twice' warnings Hans Verkuil
2014-11-05 7:44 ` Hans Verkuil
2014-11-05 10:49 ` Christopher Li [this message]
2014-11-12 15:39 ` Christopher Li
2014-12-05 13:39 ` Hans Verkuil
2014-12-09 1:11 ` Christopher Li
2014-12-12 4:32 ` Christopher Li
2014-12-12 8:04 ` Hans Verkuil
2014-12-12 8:12 ` Josh Triplett
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=CANeU7QmfgPwOk0LMaUFxaH6UzA03NUizR6ybZ58NGkPEd3OkvQ@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=hverkuil@xs4all.nl \
--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).