From: Jonathan Cameron <jic23@kernel.org>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: "Aldo Conte" <aldocontelk@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Javier Carrasco" <javier.carrasco.cruz@gmail.com>
Subject: Re: [PATCH] iio: light: veml6070: fix veml6070_read() return value
Date: Wed, 25 Mar 2026 16:35:48 +0000 [thread overview]
Message-ID: <20260325163548.0a43298c@jic23-huawei> (raw)
In-Reply-To: <510e9313c229341f963508ca480ef6e5c5342b75.camel@gmail.com>
On Wed, 25 Mar 2026 12:31:29 +0000
Nuno Sá <noname.nuno@gmail.com> wrote:
> On Wed, 2026-03-25 at 12:32 +0100, Aldo Conte wrote:
> > veml6070_read() computes the sensor value in ret but
> > returns 0 instead of the actual result. This causes
> > veml6070_read_raw() to always report 0.
> >
> > Return the computed value instead of 0.
> >
> > Running make W=1 returns no errors. I was unable
> > to test the patch because I do not have the hardware.
> > Found by code inspection.
> >
> > Fixes: bb18885ed823 ("iio: light: veml6070: add support for integration time")
> > Signed-off-by: Aldo Conte <aldocontelk@gmail.com>
> > ---
>
> Makes sense...
>
> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
>
I'm not going to try and figure out how that one got through!
Any applied and marked for stable.
Thanks,
Jonathan
> > drivers/iio/light/veml6070.c | 4 +---
> > 1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > diff --git a/drivers/iio/light/veml6070.c b/drivers/iio/light/veml6070.c
> > index 6d4483c85f30..74d7246e5225 100644
> > --- a/drivers/iio/light/veml6070.c
> > +++ b/drivers/iio/light/veml6070.c
> > @@ -134,9 +134,7 @@ static int veml6070_read(struct veml6070_data *data)
> > if (ret < 0)
> > return ret;
> >
> > - ret = (msb << 8) | lsb;
> > -
> > - return 0;
> > + return (msb << 8) | lsb;
> > }
> >
> > static const struct iio_chan_spec veml6070_channels[] = {
next prev parent reply other threads:[~2026-03-25 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 11:32 Aldo Conte
2026-03-25 12:31 ` Nuno Sá
2026-03-25 16:35 ` Jonathan Cameron [this message]
2026-03-25 23:30 ` Javier Carrasco
2026-03-26 8:23 ` Jonathan Cameron
2026-03-26 13:14 ` Aldo Conte
2026-03-26 20:23 ` 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=20260325163548.0a43298c@jic23-huawei \
--to=jic23@kernel.org \
--cc=aldocontelk@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noname.nuno@gmail.com \
--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
all inboxes | Powered by JetHome®