On Fri, Jun 26, 2015 at 2:30 AM, Grygorii Strashko <grygorii.strashko@xxxxxx> wrote: > Assign GPIO chip owner field to chip->dev->driver->owner if it was not > configured by GPIO driver. Sounds good, setting this field manually seems to make less and less sense anyway as most drivers follow the device model. > > Cc: Johan Hovold <johan@xxxxxxxxxx> > Signed-off-by: Grygorii Strashko <grygorii.strashko@xxxxxx> > --- > Hi, > > There is also one positive additional side effect: > lines like below can be removed from a lot of GPIO > drivers > rdc321x_gpio_dev->chip.owner = THIS_MODULE; A good idea for a follow-up patch! ;) Acked-by: Alexandre Courbot <acourbot@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 2/2] gpiolib: assign chip owner to dev->driver->owner if not set
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 2/2] gpiolib: assign chip owner to dev->driver->owner if not set
- From: Alexandre Courbot <gnurou@xxxxxxxxx>
- Date: Tue, 30 Jun 2015 22:41:21 +0900
- In-reply-to: <1435253451-19817-2-git-send-email-grygorii.strashko@ti.com>
- References:
- [PATCH 1/2] gpiolib: irqchip: prevent driver unloading if gpio is used as irq only
- From: Grygorii Strashko
- [PATCH 2/2] gpiolib: assign chip owner to dev->driver->owner if not set
- From: Grygorii Strashko
- [PATCH 1/2] gpiolib: irqchip: prevent driver unloading if gpio is used as irq only
- Prev by Date: [PATCH v2 5/9] arm: twr-k70f120m: IOMUX driver for Kinetis SoC
- Next by Date: Re: [PATCH] gpio: zynq: Fix problem with unbalanced pm_runtime_enable
- Previous by thread: [PATCH 2/2] gpiolib: assign chip owner to dev->driver->owner if not set
- Next by thread: Re: [PATCH 2/2] gpiolib: assign chip owner to dev->driver->owner if not set
- Index(es):
 |