From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 0/5] pinctrl: renesas: use new GPIO line value setter callbacks
Date: Thu, 12 Jun 2025 13:52:53 +0200 [thread overview]
Message-ID: <CAMuHMdVgNKgybzACevUkfuapayFZzYv4RNsARQD-RpFESc2hKQ@mail.gmail.com> (raw)
In-Reply-To: <20250611-gpiochip-set-rv-pinctrl-renesas-v1-0-ad169a794ef0@linaro.org>
On Wed, 11 Jun 2025 at 10:44, Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> Commit 98ce1eb1fd87e ("gpiolib: introduce gpio_chip setters that return
> values") added new line setter callbacks to struct gpio_chip. They allow
> to indicate failures to callers. We're in the process of converting all
> GPIO controllers to using them before removing the old ones. This series
> converts all GPIO chips in renesas pin control drivers.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> Bartosz Golaszewski (5):
> pinctrl: renesas: use new GPIO line value setter callbacks
> pinctrl: rzg2l: use new GPIO line value setter callbacks
> pinctrl: rza1: use new GPIO line value setter callbacks
> pinctrl: rzv2m: use new GPIO line value setter callbacks
> pinctrl: rza2: use new GPIO line value setter callbacks
>
> drivers/pinctrl/renesas/gpio.c | 6 ++++--
> drivers/pinctrl/renesas/pinctrl-rza1.c | 8 +++++---
> drivers/pinctrl/renesas/pinctrl-rza2.c | 8 +++++---
> drivers/pinctrl/renesas/pinctrl-rzg2l.c | 8 +++++---
> drivers/pinctrl/renesas/pinctrl-rzv2m.c | 8 +++++---
> 5 files changed, 24 insertions(+), 14 deletions(-)
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-pinctrl for v6.17.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2025-06-12 11:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 7:27 Bartosz Golaszewski
2025-06-11 7:27 ` [PATCH 1/5] " Bartosz Golaszewski
2025-06-11 10:39 ` Wolfram Sang
2025-06-11 7:27 ` [PATCH 2/5] pinctrl: rzg2l: " Bartosz Golaszewski
2025-06-11 10:43 ` Wolfram Sang
2025-06-11 7:27 ` [PATCH 3/5] pinctrl: rza1: " Bartosz Golaszewski
2025-06-11 10:41 ` Wolfram Sang
2025-06-11 7:27 ` [PATCH 4/5] pinctrl: rzv2m: " Bartosz Golaszewski
2025-06-11 10:44 ` Wolfram Sang
2025-06-11 7:27 ` [PATCH 5/5] pinctrl: rza2: " Bartosz Golaszewski
2025-06-11 10:42 ` Wolfram Sang
2025-06-11 10:44 ` [PATCH 0/5] pinctrl: renesas: " Wolfram Sang
2025-06-12 11:52 ` Geert Uytterhoeven [this message]
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=CAMuHMdVgNKgybzACevUkfuapayFZzYv4RNsARQD-RpFESc2hKQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
/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
all inboxes | Powered by JetHome®