Re: [PATCH] PM / wakeirq: check that wake IRQ is valid before accepting it

2015-11-13 Thread Rafael J. Wysocki
On Thursday, November 12, 2015 10:52:11 AM Dmitry Torokhov wrote: > On Thu, Nov 12, 2015 at 08:41:55PM +0200, Grygorii Strashko wrote: > > On 11/12/2015 08:26 PM, Dmitry Torokhov wrote: > > >Check that IRQ number passed to dev_pm_set_wake_irq and > > >dev_pm_set_dedicated_wake_irq is valid (not neg

Re: [PATCH] PM / wakeirq: check that wake IRQ is valid before accepting it

2015-11-12 Thread Dmitry Torokhov
On Thu, Nov 12, 2015 at 08:41:55PM +0200, Grygorii Strashko wrote: > On 11/12/2015 08:26 PM, Dmitry Torokhov wrote: > >Check that IRQ number passed to dev_pm_set_wake_irq and > >dev_pm_set_dedicated_wake_irq is valid (not negative) before accepting it. > > > >Signed-off-by: Dmitry Torokhov > >---

Re: [PATCH] PM / wakeirq: check that wake IRQ is valid before accepting it

2015-11-12 Thread Grygorii Strashko
On 11/12/2015 08:26 PM, Dmitry Torokhov wrote: Check that IRQ number passed to dev_pm_set_wake_irq and dev_pm_set_dedicated_wake_irq is valid (not negative) before accepting it. Signed-off-by: Dmitry Torokhov --- My recent change to i2c core introduced a code path that led to calling dev_pm_se

[PATCH] PM / wakeirq: check that wake IRQ is valid before accepting it

2015-11-12 Thread Dmitry Torokhov
Check that IRQ number passed to dev_pm_set_wake_irq and dev_pm_set_dedicated_wake_irq is valid (not negative) before accepting it. Signed-off-by: Dmitry Torokhov --- My recent change to i2c core introduced a code path that led to calling dev_pm_set_wake_irq(&client->dev, -ENOENT), which succeede