From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>, Pavel Machek <pavel@ucw.cz>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Marek Behún" <kabel@kernel.org>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v1 0/3] Get rid of devm_fwnode_get_[index_]gpiod_from_child()
Date: Mon, 7 Nov 2022 20:52:33 -0800 [thread overview]
Message-ID: <Y2ngkYVAfn24EcfL@google.com> (raw)
In-Reply-To: <CAMRc=McvJ7AvhKdP7cv8K1+rzMf8-ptg2SnU+XOAwERhRx1Eyw@mail.gmail.com>
On Tue, Oct 25, 2022 at 05:48:02PM +0200, Bartosz Golaszewski wrote:
> On Mon, Oct 24, 2022 at 2:18 PM Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> >
> > On Thu, Sep 22, 2022 at 02:48:26PM -0700, Dmitry Torokhov wrote:
> > > Hi Pavel, Marek,
> > >
> > > On Fri, Sep 02, 2022 at 05:55:24PM -0700, Dmitry Torokhov wrote:
> > > > This drops the last uses of devm_fwnode_get_[index_]gpiod_from_child()
> > > > from the tree and drops the stubs implementing this API on top of
> > > > devm_fwnode_gpiod_get_index().
> > > >
> > > > Note that the bulk of users were converted in 2019, the couple of LED
> > > > drivers are all that have remained.
> > > >
> > > > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > > >
> > > > ---
> > > > Dmitry Torokhov (3):
> > > > leds: gpio: switch to using devm_fwnode_gpiod_get()
> > > > leds: lgm-sso: switch to using devm_fwnode_gpiod_get()
> > > > gpiolib: remove devm_fwnode_get_[index_]gpiod_from_child()
> > > >
> > > > drivers/leds/blink/leds-lgm-sso.c | 5 ++---
> > > > drivers/leds/leds-gpio.c | 5 ++---
> > > > include/linux/gpio/consumer.h | 21 ---------------------
> > > > 3 files changed, 4 insertions(+), 27 deletions(-)
> > > > ---
> > > > base-commit: 7fd22855300e693668c3397771b3a2b3948f827a
> > > > change-id: 20220902-get_gpiod_from_child-remove-a62638849e91
> > > >
> > >
> > > Could you please consider picking this up for 6.1? Or would you be OK
> > > with this going through other tree (GPIO maybe)?
> >
> > *ping* Could this go through GPIO tree? Dropping this API helps with
> > some outstanding work that I have...
> >
>
> Sure! I'll let it wait for another week - it would be great to get an
> ack from Pavel - but in case of no response I'll take it through my
> tree.
Pavel, any chance we could get an Ack for this?
Thanks!
--
Dmitry
next prev parent reply other threads:[~2022-11-08 4:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 0:55 [PATCH v1 0/3] Get rid of devm_fwnode_get_[index_]gpiod_from_child() Dmitry Torokhov
2022-09-03 0:55 ` [PATCH v1 1/3] leds: gpio: switch to using devm_fwnode_gpiod_get() Dmitry Torokhov
2022-09-03 0:55 ` [PATCH v1 2/3] leds: lgm-sso: " Dmitry Torokhov
2022-09-03 0:55 ` [PATCH v1 3/3] gpiolib: remove devm_fwnode_get_[index_]gpiod_from_child() Dmitry Torokhov
2022-09-04 20:14 ` Bartosz Golaszewski
2022-09-03 9:59 ` [PATCH v1 0/3] Get rid of devm_fwnode_get_[index_]gpiod_from_child() Andy Shevchenko
2022-09-03 12:26 ` Linus Walleij
2022-09-22 21:48 ` Dmitry Torokhov
2022-10-24 12:18 ` Dmitry Torokhov
2022-10-25 15:48 ` Bartosz Golaszewski
2022-11-08 4:52 ` Dmitry Torokhov [this message]
2022-11-08 10:53 ` Linus Walleij
2022-11-09 13:00 ` Bartosz Golaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y2ngkYVAfn24EcfL@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=brgl@bgdev.pl \
--cc=kabel@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).