On Sat, Feb 25, 2017 at 2:24 AM, Stephen Boyd wrote:
> Quoting Stephen Boyd (2017-02-17 08:52:29)
>> If we call get_user() with an __le* or __be* type sparse will
>> complain when we assign the result to 0 on the faulting path.
>> Let's force cast here so that sparse doesn't complain. This
>> mirr
Quoting Stephen Boyd (2017-02-17 08:52:29)
> If we call get_user() with an __le* or __be* type sparse will
> complain when we assign the result to 0 on the faulting path.
> Let's force cast here so that sparse doesn't complain. This
> mirrors what we do in __get_user() as well.
>
> Signed-off-by:
If we call get_user() with an __le* or __be* type sparse will
complain when we assign the result to 0 on the faulting path.
Let's force cast here so that sparse doesn't complain. This
mirrors what we do in __get_user() as well.
Signed-off-by: Stephen Boyd
---
I made a similar fix to arm64 header
3 matches
Mail list logo