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 3/4] iio: frequency: ad9523: add dev variable
Date: Fri, 6 Mar 2026 16:39:09 +0200 [thread overview]
Message-ID: <aarnDSzQHIrfmSen@ashevche-desk.local> (raw)
In-Reply-To: <20260306102504.42395-4-antoniu.miclaus@analog.com>
On Fri, Mar 06, 2026 at 12:24:47PM +0200, Antoniu Miclaus wrote:
> Introduce a local struct device variable in ad9523_probe() to simplify
> subsequent conversions and improve code readability.
...
> static int ad9523_probe(struct spi_device *spi)
> {
> - struct ad9523_platform_data *pdata = dev_get_platdata(&spi->dev);
> + struct device *dev = &spi->dev;
> + struct ad9523_platform_data *pdata = dev_get_platdata(dev);
It's always better to split assignment and definition when the result is going
to be validated. It makes code robust against potential changes in
between that might alter that variable / value.
struct ad9523_platform_data *pdata;
> struct iio_dev *indio_dev;
> struct ad9523_state *st;
> int ret;
pdata = dev_get_platdata(dev);
> if (!pdata) {
> - dev_err(&spi->dev, "no platform data?\n");
> + dev_err(dev, "no platform data?\n");
This line can be updated in the second patch altogether.
> return -EINVAL;
> }
...
> - st->reset_gpio = devm_gpiod_get_optional(&spi->dev, "reset",
> + st->reset_gpio = devm_gpiod_get_optional(dev, "reset",
> GPIOD_OUT_LOW);
> if (IS_ERR(st->reset_gpio))
> return PTR_ERR(st->reset_gpio);
Side note: The material to move to reset-gpio driver instead (I think we have
tons of the IIO drivers with the same).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-06 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 10:24 [PATCH 0/4] iio: frequency: use dev_err_probe for admv4420 and ad9523 Antoniu Miclaus
2026-03-06 10:24 ` [PATCH 1/4] iio: frequency: admv4420: add dev variable Antoniu Miclaus
2026-03-06 14:41 ` Andy Shevchenko
2026-03-06 10:24 ` [PATCH 2/4] iio: frequency: admv4420: use dev_err_probe Antoniu Miclaus
2026-03-06 14:45 ` Andy Shevchenko
2026-03-06 10:24 ` [PATCH 3/4] iio: frequency: ad9523: add dev variable Antoniu Miclaus
2026-03-06 14:39 ` Andy Shevchenko [this message]
2026-03-06 10:24 ` [PATCH 4/4] iio: frequency: ad9523: use dev_err_probe Antoniu Miclaus
2026-03-06 12:24 ` Andy Shevchenko
2026-03-07 11:09 ` Jonathan Cameron
2026-03-06 12:24 ` [PATCH 0/4] iio: frequency: use dev_err_probe for admv4420 and ad9523 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=aarnDSzQHIrfmSen@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