[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZyQQ0io9dPsmAs1xyoFgo0u262SZd3B=oUgh8gdWiGFQ@mail.gmail.com>
Date: Tue, 3 Sep 2013 14:10:51 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Thierry Reding <thierry.reding@...il.com>
Cc: "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Frank Rowand <frowand.list@...il.com>
Subject: Re: [PATCH 1/2] gpio: Fix crash in gpiod_set_debounce()
On Tue, Sep 3, 2013 at 12:39 PM, Thierry Reding
<thierry.reding@...il.com> wrote:
> Return an error if neither the ->set() nor the ->set_debounce() function
> is implemented by the chip. Furthermore move locking further down so the
> lock doesn't have to be unlocked on error. This is safe to do because at
> this point the lock doesn't protect anything.
>
> Signed-off-by: Thierry Reding <treding@...dia.com>
> ---
> Linus,
>
> Feel free to squash this into the commit that introduced these:
>
> fc9bbfb: gpio: improve error path in gpiolib
Hm I fixed part of this bug yesterday, but screwed up and left the dangling
spinlock in there, what is wrong with me :-(
Anyway, fixed it _finally_ now, thanks to you.
Yours,
Linus Walleij
--
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