From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Archit Anant <architanant5@gmail.com>
Cc: jic23@kernel.org, dlechner@baylibre.com, lars@metafoo.de,
Michael.Hennerich@analog.com, nuno.sa@analog.com,
andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/4] iio: adc: ad799x: use devm_add_action_or_reset for regulators
Date: Sun, 8 Mar 2026 23:15:35 +0200 [thread overview]
Message-ID: <aa3m9y7_OW4bGAG3@ashevche-desk.local> (raw)
In-Reply-To: <20260308182811.33471-4-architanant5@gmail.com>
On Sun, Mar 08, 2026 at 11:58:10PM +0530, Archit Anant wrote:
> Convert the manual regulator_disable() handling to use
> devm_add_action_or_reset(). This guarantees that the regulators are
> disabled in the correct reverse order of allocation during device
> teardown or probe failure.
>
> As part of this conversion, introduce a local device pointer to
> simplify function calls and remove redundant goto labels for regulator
> cleanup, as the devm framework now handles these automatically.
Needs to be split to two:
- moving to managed resources (and here you introduce temporary variable to reduce the churn)
- simplifying the old code with that variable
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-08 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 18:28 [PATCH v4 0/4] iio: adc: ad799x: modernize resource management Archit Anant
2026-03-08 18:28 ` [PATCH v4 1/4] iio: adc: ad799x: make rx_buf static Archit Anant
2026-03-08 21:10 ` Andy Shevchenko
2026-03-08 18:28 ` [PATCH v4 2/4] iio: adc: ad799x: cache regulator voltage during probe Archit Anant
2026-03-08 21:12 ` Andy Shevchenko
2026-03-09 19:38 ` Jonathan Cameron
2026-03-08 18:28 ` [PATCH v4 3/4] iio: adc: ad799x: use devm_add_action_or_reset for regulators Archit Anant
2026-03-08 21:15 ` Andy Shevchenko [this message]
2026-03-08 18:28 ` [PATCH v4 4/4] iio: adc: ad799x: use devm_iio_device_register and drop remove Archit Anant
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=aa3m9y7_OW4bGAG3@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=architanant5@gmail.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®