From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
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: Wed, 11 Jun 2025 12:44:52 +0200 [thread overview]
Message-ID: <aEleJFgQxLfMpOW9@shikoro> (raw)
In-Reply-To: <20250611-gpiochip-set-rv-pinctrl-renesas-v1-0-ad169a794ef0@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
On Wed, Jun 11, 2025 at 09:27:51AM +0200, Bartosz Golaszewski 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.
Looks fine, builds fine. Thank you!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-06-11 10:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 7:27 [PATCH 0/5] pinctrl: renesas: use new GPIO line value setter callbacks 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 ` Wolfram Sang [this message]
2025-06-12 11:52 ` [PATCH 0/5] pinctrl: renesas: " Geert Uytterhoeven
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=aEleJFgQxLfMpOW9@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=geert+renesas@glider.be \
--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