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 v2 3/4] iio: frequency: ad9523: add dev variable
Date: Fri, 13 Mar 2026 16:10:23 +0200 [thread overview]
Message-ID: <abQaz0P4CLpFtFbq@ashevche-desk.local> (raw)
In-Reply-To: <cdb7e229a137c24727bbf201a725f5634a34bfe0.1773050333.git.antoniu.miclaus@analog.com>
On Fri, Mar 13, 2026 at 01:57:43PM +0200, Antoniu Miclaus wrote:
> Introduce a local struct device variable in ad9523_probe() to simplify
> subsequent conversions and improve code readability.
>
> Split pdata declaration and assignment since the result is validated
> immediately after.
>
> No functional change.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-13 14:10 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 [this message]
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 ` [PATCH v2 0/4] iio: frequency: use dev_err_probe for admv4420 and ad9523 Jonathan Cameron
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=abQaz0P4CLpFtFbq@ashevche-desk.local \
--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