From: Gregory Fong <gregory.0xf0@gmail.com>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: linux-gpio@vger.kernel.org, linus.walleij@linaro.org,
bgolaszewski@baylibre.com, f.fainelli@gmail.com,
matthias.bgg@gmail.com, opensource@vdorst.com,
andy.shevchenko@gmail.com, git@johnthomson.fastmail.com.au,
neil@brown.name, hofrat@osadl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] gpio: brcmstb: remove custom 'brcmstb_gpio_set_names'
Date: Mon, 19 Jul 2021 00:59:06 -0700 [thread overview]
Message-ID: <20210719075906.GB8818@kessel> (raw)
In-Reply-To: <20210708070429.31871-4-sergio.paracuellos@gmail.com>
On Thu, Jul 08, 2021 at 09:04:29AM +0200, Sergio Paracuellos wrote:
> Gpiolib core code has been updated to support setting
> friendly names through properly 'gpio-line-names'.
> Instead of redefine behaviour here to skip the core
> to be executed, just properly assign the desired offset
> per bank to get in the core the expected behaviour.
>
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
After the first patch is cleaned up,
Acked-by: Gregory Fong <gregory.0xf0@gmail.com>
Best regards,
Gregory
next prev parent reply other threads:[~2021-07-19 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 7:04 [PATCH 0/3] gpiolib: convert 'devprop_gpiochip_set_names' to support multiple gpiochip per device Sergio Paracuellos
2021-07-08 7:04 ` [PATCH 1/3] gpiolib: convert 'devprop_gpiochip_set_names' to support multiple gpiochip baks " Sergio Paracuellos
2021-07-19 7:57 ` Gregory Fong
2021-07-19 8:31 ` Sergio Paracuellos
2021-07-27 7:39 ` Gregory Fong
2021-07-27 11:42 ` Sergio Paracuellos
2021-07-08 7:04 ` [PATCH 2/3] gpio: mt7621: support gpio-line-names property Sergio Paracuellos
2021-07-08 7:04 ` [PATCH 3/3] gpio: brcmstb: remove custom 'brcmstb_gpio_set_names' Sergio Paracuellos
2021-07-19 7:59 ` Gregory Fong [this message]
2021-07-08 8:02 ` [PATCH 0/3] gpiolib: convert 'devprop_gpiochip_set_names' to support multiple gpiochip per device Andy Shevchenko
2021-07-08 8:40 ` Sergio Paracuellos
2021-07-27 6:02 ` Sergio Paracuellos
2021-07-27 11:35 ` Bartosz Golaszewski
2021-07-27 11:40 ` Sergio Paracuellos
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=20210719075906.GB8818@kessel \
--to=gregory.0xf0@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=f.fainelli@gmail.com \
--cc=git@johnthomson.fastmail.com.au \
--cc=hofrat@osadl.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=neil@brown.name \
--cc=opensource@vdorst.com \
--cc=sergio.paracuellos@gmail.com \
/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