From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Michael Tretter <m.tretter@pengutronix.de>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-gpio@vger.kernel.org, kernel@pengutronix.de,
Stefan Kerkmann <s.kerkmann@pengutronix.de>
Subject: Re: [PATCH v2 1/2] gpiolib: introduce devm_fwnode_gpiod_get_optional() wrapper
Date: Tue, 27 Jan 2026 08:53:46 +0200 [thread overview]
Message-ID: <33097246-9724-4e9f-a06d-efab2bb001cb@gmail.com> (raw)
In-Reply-To: <20260126-gpio-devm_fwnode_gpiod_get_optional-v2-1-ec34f8e35077@pengutronix.de>
On 26/01/2026 16:27, Michael Tretter wrote:
> From: Stefan Kerkmann <s.kerkmann@pengutronix.de>
>
> The helper makes it easier to handle optional GPIOs and simplifies the
> error handling code.
>
> Signed-off-by: Stefan Kerkmann <s.kerkmann@pengutronix.de>
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
FWIW:
Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>
Yours,
-- Matti
---
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2026-01-27 6:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 14:27 [PATCH v2 0/2] gpiolib: introduce devm_fwnode_gpiod_get_optional Michael Tretter
2026-01-26 14:27 ` [PATCH v2 1/2] gpiolib: introduce devm_fwnode_gpiod_get_optional() wrapper Michael Tretter
2026-01-27 6:53 ` Matti Vaittinen [this message]
2026-01-27 19:40 ` Andy Shevchenko
2026-01-26 14:27 ` [PATCH v2 2/2] regulator: bd71815: switch to devm_fwnode_gpiod_get_optional Michael Tretter
2026-01-27 9:17 ` [PATCH v2 0/2] gpiolib: introduce devm_fwnode_gpiod_get_optional 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=33097246-9724-4e9f-a06d-efab2bb001cb@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=s.kerkmann@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.