On Thu, Sep 3, 2015 at 7:34 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > If the gpio driver is confused about the numbers for gpio-ranges, > pinctrl_ready_for_gpio_range() may get called with invalid GPIO > causing a NULL pointer exception. Let's instead provide a warning > that allows fixing the problem and return with error. > > Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx> Patch applied for fixes. Yours, Linus Walleij -- 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] pinctrl: core: Warn about NULL gpio_chip in pinctrl_ready_for_gpio_range()
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH] pinctrl: core: Warn about NULL gpio_chip in pinctrl_ready_for_gpio_range()
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Tue, 8 Sep 2015 16:11:42 +0200
- In-reply-to: <1441301670-6498-1-git-send-email-tony@atomide.com>
- References:
- Prev by Date: Re: [patch 15/22] pinctrl: Use irq_desc_get_xxx() to avoid redundant lookup of irq_desc
- Next by Date: Re: [PATCH] gpio: omap: Fix GPIO numbering for deferred probe
- Previous by thread: [PATCH] pinctrl: core: Warn about NULL gpio_chip in pinctrl_ready_for_gpio_range()
- Next by thread: [GIT PULL] bulk of pin control changes for v4.3
- Index(es):
 |