From: David Lechner <dlechner@baylibre.com>
To: "Salah Triki" <salah.triki@gmail.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Marcelo Schmitt" <marcelo.schmitt@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"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] iio: adc: ad4170-4: Use ERR_PTR() with %pe to improve error logging
Date: Thu, 7 Aug 2025 11:02:57 -0500 [thread overview]
Message-ID: <fe98c2a2-ec8d-4352-a9fb-6f0e798f7268@baylibre.com> (raw)
In-Reply-To: <aJReTh-t5D45aZNV@pc>
On 8/7/25 3:05 AM, Salah Triki wrote:
> Use `ERR_PTR(ret)` with `%pe` in `ad4170_read_sample()` to properly display
> symbolic error codes (e.g. `-ENOMEM`) instead of raw integers (e.g. `-12`),
> improving readability and debug clarity.
>
> Signed-off-by: Salah Triki <salah.triki@gmail.com>
> ---
> Changes in v2:
> - Improve commit title
>
> drivers/iio/adc/ad4170-4.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/adc/ad4170-4.c b/drivers/iio/adc/ad4170-4.c
> index 6cd84d6fb08b..6296b5dc930b 100644
> --- a/drivers/iio/adc/ad4170-4.c
> +++ b/drivers/iio/adc/ad4170-4.c
> @@ -1253,11 +1253,11 @@ static int ad4170_read_sample(struct iio_dev *indio_dev,
>
> ret = __ad4170_read_sample(indio_dev, chan, val);
> if (ret) {
> - dev_err(dev, "failed to read sample: %d\n", ret);
> + dev_err(dev, "failed to read sample: %pe\n", ERR_PTR(ret));
>
> ret2 = ad4170_set_channel_enable(st, chan->address, false);
> if (ret2)
> - dev_err(dev, "failed to disable channel: %d\n", ret2);
> + dev_err(dev, "failed to disable channel: %pe\n", ERR_PTR(ret2));
>
> return ret;
> }
Interesting, I didn't know we had this format specifier. But I think
this is something we would want to do kernel-wide or not at all to stay
consistent.
And if we are doing this in more places, it would make sense to have a new
format specifier for integer error values instead of casting them to
pointers.
next prev parent reply other threads:[~2025-08-07 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 8:05 Salah Triki
2025-08-07 16:02 ` David Lechner [this message]
2025-08-07 21:01 ` Andy Shevchenko
2025-08-07 21:02 ` Andy Shevchenko
2025-08-07 21:14 ` David Lechner
2025-08-07 21:20 ` Andy Shevchenko
2025-08-08 12:07 ` Marcelo Schmitt
2025-08-08 12:30 ` Andy Shevchenko
2025-08-08 14:43 ` 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=fe98c2a2-ec8d-4352-a9fb-6f0e798f7268@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt@analog.com \
--cc=nuno.sa@analog.com \
--cc=salah.triki@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
all inboxes | Powered by JetHome®