From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"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 v2 0/4] iio: frequency: use dev_err_probe for admv4420 and ad9523
Date: Sat, 21 Mar 2026 21:13:07 +0000 [thread overview]
Message-ID: <20260321211307.4d1e5cd3@jic23-huawei> (raw)
In-Reply-To: <cover.1773050333.git.antoniu.miclaus@analog.com>
On Fri, 13 Mar 2026 13:57:40 +0200
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
> Use dev_err_probe() instead of dev_err() in the probe paths of the
> admv4420 and ad9523 frequency drivers.
>
> Each driver update is split into two patches:
> - First patch introduces a local struct device variable in the probe
> function and replaces &spi->dev references in non-error paths.
> - Second patch converts dev_err() calls to dev_err_probe() in the
> probe path.
>
> No lines are edited twice across patch pairs.
Series applied to the testing branch of iio.git.
Usual stuff about will wait for bots to poke it then push out as togreg
for linux-next to pick it up.
thanks,
Jonathan
>
> Changes in v2:
> - Fix vco_freq_hz format specifier from %lld to %llu (patch 2)
> - Split pdata declaration and assignment in ad9523_probe() (patch 3)
> - Leave dev_err(&spi->dev, ...) untouched in patch 3, let patch 4
> handle the full dev_err_probe(dev, ...) conversion
>
> Antoniu Miclaus (4):
> iio: frequency: admv4420: add dev variable
> iio: frequency: admv4420: use dev_err_probe
> iio: frequency: ad9523: add dev variable
> iio: frequency: ad9523: use dev_err_probe
>
> drivers/iio/frequency/ad9523.c | 22 ++++++++++----------
> drivers/iio/frequency/admv4420.c | 35 +++++++++++++++-----------------
> 2 files changed, 27 insertions(+), 30 deletions(-)
>
prev parent reply other threads:[~2026-03-21 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 11:57 [PATCH v2 0/4] iio: frequency: use dev_err_probe for admv4420 and ad9523 Antoniu Miclaus
2026-03-13 11:57 ` [PATCH v2 1/4] iio: frequency: admv4420: add dev variable Antoniu Miclaus
2026-03-13 11:57 ` [PATCH v2 2/4] iio: frequency: admv4420: use dev_err_probe Antoniu Miclaus
2026-03-13 11:57 ` [PATCH v2 3/4] iio: frequency: ad9523: add dev variable Antoniu Miclaus
2026-03-13 14:10 ` Andy Shevchenko
2026-03-13 11:57 ` [PATCH v2 4/4] iio: frequency: ad9523: use dev_err_probe Antoniu Miclaus
2026-03-13 14:11 ` Andy Shevchenko
2026-03-21 21:13 ` 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=20260321211307.4d1e5cd3@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=dlechner@baylibre.com \
--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