On Tue, May 6, 2014 at 1:47 AM, Dan Carpenter <dan.carpenter@xxxxxxxxxx> wrote:
>> - bool search_dir[4] = {0, 0, 0, 0};
>> + bool search_dir[4] = {0};
>
> That's weird. The original code is valid but it generates a sparse
> warning.
>
> drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c:244:58: warning: Initializer entry defined twice
> drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c:244:61: also defined here
>
> It has something to do with "_Bool" types. Changing it to "int" will
> also make the warning disappear. I've CC'd the sparse list to see if
> anyone knows what's happening.
This is easy reproducible with a small test case. It is a sparse bug for sure.
Let me take a look.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
