[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAVeFuLpBjnA0uq6vjpawWpzEG76sDe7pCgS6nG6CwGaar-JKA@mail.gmail.com>
Date: Tue, 30 Jun 2015 22:41:21 +0900
From: Alexandre Courbot <gnurou@...il.com>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Sekhar Nori <nsekhar@...com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Johan Hovold <johan@...nel.org>
Subject: Re: [PATCH 2/2] gpiolib: assign chip owner to dev->driver->owner if
not set
On Fri, Jun 26, 2015 at 2:30 AM, Grygorii Strashko
<grygorii.strashko@...com> 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@...nel.org>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@...com>
> ---
> 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@...dia.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists