From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] iio: use dev_err_probe in probe path for ADI drivers
Date: Wed, 25 Feb 2026 18:15:04 +0200 [thread overview]
Message-ID: <aZ8gCD3YXvrNscQo@smile.fi.intel.com> (raw)
In-Reply-To: <20260225150615.274078-1-antoniu.miclaus@analog.com>
On Wed, Feb 25, 2026 at 05:05:46PM +0200, Antoniu Miclaus wrote:
> Use dev_err_probe() consistently in the probe path of several ADI IIO
> drivers. This simplifies error handling and ensures proper logging of
> deferred probes.
>
> Each driver is updated by introducing a local struct device variable to
> simplify repeated &spi->dev / &client->dev references, and converting
> error paths to use dev_err_probe().
>
> Drivers updated:
> - adrf6780
> - admv1014
> - admv1013
> - adf4377
> - ad7293
> - admv8818
>
> Changes in v3:
> - Squash the struct device variable introduction and dev_err_probe()
> conversion into a single patch per driver.
Why? Maybe my comment was unclear previous time.
The idea is to convert to short dev the only lines that are not being touched
by the second (dev_err_probe() conversion) patch.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-25 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 15:05 [PATCH v3 0/6] iio: use dev_err_probe in probe path for ADI drivers Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 1/6] iio: frequency: adrf6780: add dev variable and use dev_err_probe Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 2/6] iio: frequency: admv1014: " Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 3/6] iio: frequency: admv1013: " Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 4/6] iio: frequency: adf4377: " Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 5/6] iio: dac: ad7293: " Antoniu Miclaus
2026-02-25 15:05 ` [PATCH v3 6/6] iio: filter: admv8818: " Antoniu Miclaus
2026-02-25 16:15 ` Andy Shevchenko [this message]
2026-02-27 11:23 ` [PATCH v3 0/6] iio: use dev_err_probe in probe path for ADI drivers Miclaus, Antoniu
2026-02-27 14:48 ` Andy Shevchenko
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=aZ8gCD3YXvrNscQo@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.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