[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025042523-immovable-onyx-e648@gregkh>
Date: Fri, 25 Apr 2025 15:22:33 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Zijun Hu <quic_zijuhu@...cinc.com>,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Raag Jadav <raag.jadav@...el.com>, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, "Rafael J. Wysocki" <rafael@...nel.org>,
Danilo Krummrich <dakr@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>
Subject: Re: [PATCH v2 0/3] gpiolib: finish conversion to devm_*_action*()
APIs
On Tue, Apr 22, 2025 at 09:55:02PM +0300, Andy Shevchenko wrote:
> On Thu, Feb 20, 2025 at 06:20:25PM +0200, Andy Shevchenko wrote:
> > GPIOLIB has some open coded stuff that can be folded to the devm_*_action*()
> > calls. This mini-series is for that. The necessary prerequisites are here
> > as well, namely:
> > 1) moving the respective APIs to the devres.h;
> > 2) adding a simple helper that GPIOLIB will rely on;
> > 3) finishing the GPIOLIB conversion to the device managed action APIs.
> >
> > The series is based on another series that's available via immutable tag
> > devres-iio-input-pinctrl-v6.15 [1]. The idea is to route this via GPIOLIB
> > tree (or Intel GPIO for the starter) with an immutable tag for the device
> > core and others if needed. Please, review and acknowledge.
>
> Greg, I know you are busy, but do you have a chance to look at this and give
> your Ack if you are okay with the idea? The route is assumed to be via GPIOLIB
> tree.
Looks fine to me:
Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Powered by blists - more mailing lists