[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJhHMCCXUJyyxPe=HFcR_YtihwkLEg96X81W8R7FKpsYb78Z9w@mail.gmail.com>
Date: Fri, 19 Sep 2014 19:35:09 -0400
From: Pranith Kumar <bobby.prani@...il.com>
To: Josh Triplett <josh@...htriplett.org>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Steven Rostedt <rostedt@...dmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Lai Jiangshan <laijs@...fujitsu.com>,
"open list:READ-COPY UPDATE..." <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] rcu: Change use of __this_cpu ops on a bool type
On Fri, Sep 19, 2014 at 4:57 PM, Josh Triplett <josh@...htriplett.org> wrote:
> On Fri, Sep 19, 2014 at 01:26:03PM -0400, Pranith Kumar wrote:
>> __this_cpu_{read/write}() uses sizeof() to determine the size of the variable.
>> Using this operation on a bool type causes sparse to complain.
>>
>> I checked the generated code and there is only a slight difference in
>> instructions generated.
>>
>> I am not sure this warning by sparse is really valid, but let us silence it
>> anyways.
>>
>> Signed-off-by: Pranith Kumar <bobby.prani@...il.com>
>
> I believe this warning was actually fixed with current versions of
> Sparse; there was some discussion and a patch on the linux-sparse
> mailing list. Can you please recheck with the latest Sparse from git,
> and if it still breaks, please raise that on linux-sparse?
>
Yup, looks like the latest version of sparse fixes this. Please ignore
this patch. Thanks!
--
Pranith
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists