From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Prashant Rahul" <prashantrahul23@gmail.com>,
linux-iio@vger.kernel.org, "Shuah Khan" <shuahkhan@gmail.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Petr Mladek" <pmladek@suse.com>,
"Oleg Nesterov" <oleg@redhat.com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"John Ogness" <john.ogness@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] iio: adc: ti-adc084s021: use dev_err_probe for probe time error
Date: Fri, 3 Jul 2026 01:35:01 +0100 [thread overview]
Message-ID: <20260703013451.75cacf98@jic23-huawei> (raw)
In-Reply-To: <99507afa-6986-44f7-98c1-257c52a5dcd4@baylibre.com>
On Fri, 19 Jun 2026 09:49:19 -0500
David Lechner <dlechner@baylibre.com> wrote:
> On 6/18/26 6:14 PM, Prashant Rahul wrote:
> > This simplifies error handling and ensures consistent error reporting.
> >
> > Signed-off-by: Prashant Rahul <prashantrahul23@gmail.com>
> > ---
> > drivers/iio/adc/ti-adc084s021.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/drivers/iio/adc/ti-adc084s021.c b/drivers/iio/adc/ti-adc084s021.c
> > index a100f770fa1c..9c7ee09955ca 100644
> > --- a/drivers/iio/adc/ti-adc084s021.c
> > +++ b/drivers/iio/adc/ti-adc084s021.c
> > @@ -230,8 +230,7 @@ static int adc084s021_probe(struct spi_device *spi)
> > adc084s021_buffer_trigger_handler,
> > &adc084s021_buffer_setup_ops);
> > if (ret) {
> > - dev_err(&spi->dev, "Failed to setup triggered buffer\n");
> > - return ret;
> > + return dev_err_probe(&spi->dev, ret, "Failed to setup triggered buffer\n");
> > }
>
>
> Can drop the braces here
>
Dropped whilst applying. I'm a bit in two minds on whether we should print
anything on this one given the incredibly low chance of anyone having
a bug that double registers the buffer - still better as dev_err_probe()
then dev_err() so applied.
> >
> > return devm_iio_device_register(&spi->dev, indio_dev);
>
next prev parent reply other threads:[~2026-07-03 0:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 13:05 [PATCH] iio: adc: ti-adc*: use dev_err_probe for probe time errors Prashant Rahul
2026-06-16 14:03 ` David Lechner
2026-06-18 16:52 ` Prashant Rahul
2026-06-23 19:31 ` Jonathan Cameron
2026-06-23 19:51 ` Andy Shevchenko
2026-06-18 23:14 ` [PATCH 0/5] use dev_err_probe for probe time error Prashant Rahul
2026-06-18 23:14 ` [PATCH 1/5] iio: adc: ti-adc081c: " Prashant Rahul
2026-07-03 0:32 ` Jonathan Cameron
2026-06-18 23:14 ` [PATCH 2/5] iio: adc: ti-adc084s021: " Prashant Rahul
2026-06-19 14:49 ` David Lechner
2026-07-03 0:35 ` Jonathan Cameron [this message]
2026-06-18 23:14 ` [PATCH 3/5] iio: adc: ti-adc108s102: log buffer setup failure in probe Prashant Rahul
2026-07-03 0:36 ` Jonathan Cameron
2026-06-18 23:14 ` [PATCH 4/5] iio: adc: ti-adc161s626: " Prashant Rahul
2026-06-18 23:14 ` [PATCH 5/5] iio: adc: ti-adc0832: " Prashant Rahul
2026-06-19 14:48 ` [PATCH 0/5] use dev_err_probe for probe time error David Lechner
2026-06-20 17:39 ` Prashant Rahul
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=20260703013451.75cacf98@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=dlechner@baylibre.com \
--cc=john.ogness@linutronix.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=oleg@redhat.com \
--cc=pmladek@suse.com \
--cc=prashantrahul23@gmail.com \
--cc=shuahkhan@gmail.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