On Tue, Sep 30, 2014 at 4:15 PM, Pramod Gurav
<[email protected]> wrote:
> Some driver in gpio still check for return value from gpiochip_remove
> Get rid of the check for return value.
>
> Cc: Linus Walleij <[email protected]>
> Cc: Alexandre Courbot <[email protected]>
> Cc: [email protected]
>
> Signed-off-by: Pramod Gurav <[email protected]>
This is already fixed in the GPIO tree, and in linux-next.
I have got more patches like this from other people, and cannot
quite understand what kind of tree you are actually looking at?
Yours,
Linus Walleij
On Wednesday 01 October 2014 01:13 PM, Linus Walleij wrote:
> On Tue, Sep 30, 2014 at 4:15 PM, Pramod Gurav
> <[email protected]> wrote:
>
>> Some driver in gpio still check for return value from gpiochip_remove
>> Get rid of the check for return value.
>>
>> Cc: Linus Walleij <[email protected]>
>> Cc: Alexandre Courbot <[email protected]>
>> Cc: [email protected]
>>
>> Signed-off-by: Pramod Gurav <[email protected]>
>
> This is already fixed in the GPIO tree, and in linux-next.
>
> I have got more patches like this from other people, and cannot
> quite understand what kind of tree you are actually looking at?
>
Sorry for this Linus. I have applied these patches on linux-next's
3.17-rc6. Just checked the other patch fixing these have come after rc6.
Should have done on master or gpio tree master.
Will be more careful next time.
> Yours,
> Linus Walleij
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>