Re: [PATCH next] gpiolib: check for parent device in devprop_gpiochip_set_names()

2020-09-16 Thread Anders Roxell
On Wed, 16 Sep 2020 at 16:47, Bartosz Golaszewski wrote: > > On Wed, Sep 16, 2020 at 4:29 PM Andy Shevchenko > wrote: > > > > On Wed, Sep 16, 2020 at 03:43:27PM +0200, Bartosz Golaszewski wrote: > > > From: Bartosz Golaszewski > > > > > > It's possible for a GPIO chip to not have a parent device

Re: [PATCH next] gpiolib: check for parent device in devprop_gpiochip_set_names()

2020-09-16 Thread Andy Shevchenko
On Wed, Sep 16, 2020 at 03:43:27PM +0200, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > It's possible for a GPIO chip to not have a parent device (whose > properties we inspect for 'gpio-line-names'). In this case we should > simply return from devprop_gpiochip_set_names(). Add an ap

Re: [PATCH next] gpiolib: check for parent device in devprop_gpiochip_set_names()

2020-09-16 Thread Bartosz Golaszewski
On Wed, Sep 16, 2020 at 4:29 PM Andy Shevchenko wrote: > > On Wed, Sep 16, 2020 at 03:43:27PM +0200, Bartosz Golaszewski wrote: > > From: Bartosz Golaszewski > > > > It's possible for a GPIO chip to not have a parent device (whose > > properties we inspect for 'gpio-line-names'). In this case we

[PATCH next] gpiolib: check for parent device in devprop_gpiochip_set_names()

2020-09-16 Thread Bartosz Golaszewski
From: Bartosz Golaszewski It's possible for a GPIO chip to not have a parent device (whose properties we inspect for 'gpio-line-names'). In this case we should simply return from devprop_gpiochip_set_names(). Add an appropriate check for this use-case. Fixes: 7cba1a4d5e16 ("gpiolib: generalize d