From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Marius Cristea <marius.cristea@microchip.com>,
Marcus Folkesson <marcus.folkesson@gmail.com>,
Kent Gustavsson <kent@minoris.se>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] iio: use devm_regulator_get_enable_read_voltage round 3
Date: Sat, 20 Jul 2024 13:50:33 +0100 [thread overview]
Message-ID: <20240720135033.3399e83e@jic23-huawei> (raw)
In-Reply-To: <20240712-iio-regulator-refactor-round-3-v1-0-835017bae43d@baylibre.com>
On Fri, 12 Jul 2024 11:03:51 -0500
David Lechner <dlechner@baylibre.com> wrote:
> This is the third round of patches to convert IIO drivers to use the
> new devm_regulator_get_enable_read_voltage() helper function.
>
> This time, we are converting some Microchip drivers. These weren't as
> trivial as some other drivers because of nested functions that need
> to know info about the reference voltage, but for the most part, should
> be fairly straightforward. And there is a bonus to remove a remove()
> callback in one of the drivers.
Applied 1-4 and 6. Comment outstanding on 5 so I'm assuming I'll see
a v2 of just that patch at somepoint.
Thanks,
Jonathan
>
> ---
> David Lechner (6):
> iio: dac: mcp4728: rename err to ret in probe function
> iio: dac: mcp4728: use devm_regulator_get_enable_read_voltage()
> iio: dac: mcp4922: use devm_regulator_get_enable_read_voltage()
> iio: dac: mcp4922: drop remove() callback
> iio: adc: mcp3564: use devm_regulator_get_enable_read_voltage()
> iio: adc: mcp3911: use devm_regulator_get_enable_read_voltage()
>
> drivers/iio/adc/mcp3564.c | 54 +++++++++++++------------------------------
> drivers/iio/adc/mcp3911.c | 59 +++++++++++++----------------------------------
> drivers/iio/dac/mcp4728.c | 45 +++++++++++-------------------------
> drivers/iio/dac/mcp4922.c | 47 ++++++-------------------------------
> 4 files changed, 52 insertions(+), 153 deletions(-)
> ---
> base-commit: 986da024b99a72e64f6bdb3f3f0e52af024b1f50
> change-id: 20240712-iio-regulator-refactor-round-3-17f2a82d2181
prev parent reply other threads:[~2024-07-20 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 16:03 [PATCH 0/6] iio: use devm_regulator_get_enable_read_voltage round 3 David Lechner
2024-07-12 16:03 ` [PATCH 1/6] iio: dac: mcp4728: rename err to ret in probe function David Lechner
2024-07-12 16:03 ` [PATCH 2/6] iio: dac: mcp4728: use devm_regulator_get_enable_read_voltage() David Lechner
2024-07-12 16:03 ` [PATCH 3/6] iio: dac: mcp4922: " David Lechner
2024-07-12 16:03 ` [PATCH 4/6] iio: dac: mcp4922: drop remove() callback David Lechner
2024-07-12 16:03 ` [PATCH 5/6] iio: adc: mcp3564: use devm_regulator_get_enable_read_voltage() David Lechner
2024-07-17 13:02 ` Marius.Cristea
2024-07-12 16:03 ` [PATCH 6/6] iio: adc: mcp3911: " David Lechner
2024-07-13 5:48 ` Marcus Folkesson
2024-07-20 12:50 ` Jonathan Cameron [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=20240720135033.3399e83e@jic23-huawei \
--to=jic23@kernel.org \
--cc=broonie@kernel.org \
--cc=dlechner@baylibre.com \
--cc=kent@minoris.se \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=marius.cristea@microchip.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;
as well as URLs for NNTP newsgroup(s).