From: "Prashant Rahul" <prashantrahul23@gmail.com>
To: "Jonathan Cameron" <jic23@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>
Cc: "Prashant Rahul" <prashantrahul23@gmail.com>,
linux-iio@vger.kernel.org,
"David Lechner" <dlechner@baylibre.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 v2 4/5] iio: adc: ti-adc161s626: log buffer setup failure in probe
Date: Sat, 04 Jul 2026 21:20:46 +0530 [thread overview]
Message-ID: <DJPWN45EI416.1GR6QTDHBU6SC@gmail.com> (raw)
In-Reply-To: <20260703013907.57b0f114@jic23-huawei>
On Fri Jul 3, 2026 at 6:09 AM IST, Jonathan Cameron wrote:
> For now I've picked up the two straight conversions to dev_err_probe()
> because I'm keen to (slowly) stop using dev_err() in probe functions.
I can look for places where dev_err() is used and can be replaced with
dev_err_probe() in other probe functions, then create a new patch
series for it. Without adding new logs or removing any existing ones, of course.
Shouldn't take a lot of time, what do you think?
next prev parent reply other threads:[~2026-07-04 15:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 17:40 [PATCH v2 0/5] Using dev_err_probe as it simplifies error handling and ensures consistent error reporting Prashant Rahul
2026-06-20 17:40 ` [PATCH v2 1/5] iio: adc: ti-adc081c: use dev_err_probe for probe time error Prashant Rahul
2026-06-20 17:40 ` [PATCH v2 2/5] iio: adc: ti-adc084s021: " Prashant Rahul
2026-06-23 10:37 ` Andy Shevchenko
2026-06-20 17:40 ` [PATCH v2 3/5] iio: adc: ti-adc108s102: log buffer setup failure in probe Prashant Rahul
2026-06-20 17:40 ` [PATCH v2 4/5] iio: adc: ti-adc161s626: " Prashant Rahul
2026-06-23 19:36 ` Jonathan Cameron
2026-06-23 19:55 ` Andy Shevchenko
2026-06-24 10:13 ` Prashant Rahul
2026-06-24 11:26 ` Andy Shevchenko
2026-06-25 11:09 ` Jonathan Cameron
2026-06-25 14:03 ` Andy Shevchenko
2026-07-03 0:39 ` Jonathan Cameron
2026-07-04 15:50 ` Prashant Rahul [this message]
2026-07-04 17:00 ` Andy Shevchenko
2026-07-04 17:28 ` Prashant Rahul
2026-07-04 18:57 ` Andy Shevchenko
2026-06-20 17:40 ` [PATCH v2 5/5] iio: adc: ti-adc0832: " Prashant Rahul
2026-06-23 10:39 ` Andy Shevchenko
2026-06-23 10:35 ` [PATCH v2 0/5] Using dev_err_probe as it simplifies error handling and ensures consistent error reporting 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=DJPWN45EI416.1GR6QTDHBU6SC@gmail.com \
--to=prashantrahul23@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--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 \
/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