From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "Salah Triki" <salah.triki@gmail.com>,
"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] iio: proximity: isl29501: Fix return type of isl29501_register_write
Date: Mon, 21 Sep 2026 00:58:06 +0100 [thread overview]
Message-ID: <20260921005806.56c74e59@jic23-hlaptop> (raw)
In-Reply-To: <20260917152339.00004fd4@gmail.com>
On Thu, 17 Sep 2026 15:23:39 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> On Thu, 17 Sep 2026 14:00:52 +0100
> Salah Triki <salah.triki@gmail.com> wrote:
>
> > isl29501_register_write() was returning a u32 instead of an int.
> > Since the function returns negative error codes (such as -ERANGE or
> > return values from i2c_smbus_write_byte_data()), returning an unsigned
> > integer type prevents callers from correctly checking for negative error
> > conditions.
> >
> > Fix this by changing the function return type from u32 to int.
> >
> > This was found through manual code review.
> >
> > Fixes: 1c28799257bc ("iio: light: isl29501: Add support for the ISL29501 ToF sensor.")
> > Signed-off-by: Salah Triki <salah.triki@gmail.com>
> > ---
>
> Makes sense. I'd mark this for stable.
>
> Reviewed-by: Joshua Crofts <joshua.crofts1@gmail.com>
Applied and marked for stable. Note this doesn't mean it will
go upstream particularly quickly. Most likely I'll be folding
the fixes into the pull request for the next merge window.
Thanks,
Jonathan
>
prev parent reply other threads:[~2026-09-20 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 13:00 [PATCH] iio: proximity: isl29501: Fix return type of isl29501_register_write Salah Triki
2026-09-17 13:23 ` Joshua Crofts
2026-09-20 23:58 ` Jonathan Cameron [this message]
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=20260921005806.56c74e59@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=joshua.crofts1@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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