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 1/7] iio: frequency: adrf6780: use dev_err_probe in probe path
Date: Fri, 20 Feb 2026 15:58:36 +0200 [thread overview]
Message-ID: <aZhojCK9R_iPFcLi@smile.fi.intel.com> (raw)
In-Reply-To: <aZhoJlYUzuHXSGXL@smile.fi.intel.com>
On Fri, Feb 20, 2026 at 03:56:58PM +0200, Andy Shevchenko wrote:
> On Fri, Feb 20, 2026 at 03:11:39PM +0200, Antoniu Miclaus wrote:
...
> > ret = __adrf6780_spi_update_bits(st, ADRF6780_REG_CONTROL,
> > ADRF6780_SOFT_RESET_MSK,
> > FIELD_PREP(ADRF6780_SOFT_RESET_MSK, 1));
> > - if (ret) {
> > - dev_err(&spi->dev, "ADRF6780 SPI software reset failed.\n");
> > - return ret;
> > - }
> > + if (ret)
> > + return dev_err_probe(&spi->dev, ret,
> > + "ADRF6780 SPI software reset failed.\n");
>
> Consider adding
>
> struct device *dev = &spi->dev;
>
> at the top, so this line becomes
>
> return dev_err_probe(dev, ret, "ADRF6780 SPI software reset failed.\n");
>
> (while at it, I would dare to drop 'SPI' from the message as is easy to derive that
> the device in question is connected to SPI bus.)
>
> return dev_err_probe(dev, ret, "ADRF6780 software reset failed.\n");
...
> Ditto for the rest.
And also for the entire series (except patch 5 where it seems already
the case).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-20 13:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 13:11 [PATCH 0/7] iio: use dev_err_probe in probe path for ADI drivers Antoniu Miclaus
2026-02-20 13:11 ` [PATCH 1/7] iio: frequency: adrf6780: use dev_err_probe in probe path Antoniu Miclaus
2026-02-20 13:56 ` Andy Shevchenko
2026-02-20 13:58 ` Andy Shevchenko [this message]
2026-02-20 14:41 ` Miclaus, Antoniu
2026-02-20 14:51 ` Andy Shevchenko
2026-02-22 16:58 ` Jonathan Cameron
2026-02-20 13:11 ` [PATCH 2/7] iio: frequency: admv1014: " Antoniu Miclaus
2026-02-20 13:11 ` [PATCH 3/7] iio: frequency: admv1013: " Antoniu Miclaus
2026-02-20 13:11 ` [PATCH 4/7] iio: frequency: adf4377: " Antoniu Miclaus
2026-02-20 13:11 ` [PATCH 5/7] iio: adc: ade9000: " Antoniu Miclaus
2026-02-22 17:01 ` Jonathan Cameron
2026-02-20 13:11 ` [PATCH 6/7] iio: dac: ad7293: " Antoniu Miclaus
2026-02-20 13:11 ` [PATCH 7/7] iio: filter: admv8818: " Antoniu Miclaus
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=aZhojCK9R_iPFcLi@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
Powered by JetHome