On Tue, Jan 02, 2018 at 11:23:14AM +0100, Linus Walleij wrote: > The error path was leaking a gpio_chip at one point. > > Cc: Johan Hovold <johan@xxxxxxxxxx> > Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx> Reviewed-by: Johan Hovold <johan@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] gpio: omap: Fix error path on chip init
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] gpio: omap: Fix error path on chip init
- From: Johan Hovold <johan@xxxxxxxxxx>
- Date: Tue, 2 Jan 2018 11:39:55 +0100
- In-reply-to: <20180102102314.12906-1-linus.walleij@linaro.org>
- References: <20180102102314.12906-1-linus.walleij@linaro.org>
- User-agent: Mutt/1.7.2 (2016-11-26)
- References:
- [PATCH] gpio: omap: Fix error path on chip init
- From: Linus Walleij
- [PATCH] gpio: omap: Fix error path on chip init
- Prev by Date: [PATCH v2] gpio: omap: Give unique labels to each GPIO bank/chip
- Next by Date: Re: [PATCH v2 3/3] gpio: rcar: Use WAKEUP_PATH driver PM flag
- Previous by thread: [PATCH] gpio: omap: Fix error path on chip init
- Next by thread: Re: [PATCH] gpio: omap: Fix error path on chip init
- Index(es):
 |