From: Jonathan Cameron <jic23@kernel.org>
To: Miaoqian Lin <linmq006@gmail.com>
Cc: Song Qiang <songqiang1304521@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Ivan Drobyshevskyi <drobyshevskyi@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: proximity: vl53l0x: Fix return value check of wait_for_completion_timeout
Date: Sat, 16 Apr 2022 14:59:06 +0100 [thread overview]
Message-ID: <20220416145906.1162767c@jic23-huawei> (raw)
In-Reply-To: <20220412064210.10734-1-linmq006@gmail.com>
On Tue, 12 Apr 2022 06:42:09 +0000
Miaoqian Lin <linmq006@gmail.com> wrote:
> wait_for_completion_timeout() returns unsigned long not int.
> It returns 0 if timed out, and positive if completed.
> The check for <= 0 is ambiguous and should be == 0 here
> indicating timeout which is the only error case.
>
> Fixes: 3cef2e31b54b ("iio: proximity: vl53l0x: Add IRQ support")
> Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
Hi,
Applied to the togreg branch of iio.git ready for the next
merge window. I'm not rushing this in because it's removing pointless
and misleading code rather than fixing a bug as such.
Thanks,
Jonathan
> ---
> Changes in v2:
> - add driver name in patch subject.
> ---
> drivers/iio/proximity/vl53l0x-i2c.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/proximity/vl53l0x-i2c.c b/drivers/iio/proximity/vl53l0x-i2c.c
> index 661a79ea200d..a284b20529fb 100644
> --- a/drivers/iio/proximity/vl53l0x-i2c.c
> +++ b/drivers/iio/proximity/vl53l0x-i2c.c
> @@ -104,6 +104,7 @@ static int vl53l0x_read_proximity(struct vl53l0x_data *data,
> u16 tries = 20;
> u8 buffer[12];
> int ret;
> + unsigned long time_left;
>
> ret = i2c_smbus_write_byte_data(client, VL_REG_SYSRANGE_START, 1);
> if (ret < 0)
> @@ -112,10 +113,8 @@ static int vl53l0x_read_proximity(struct vl53l0x_data *data,
> if (data->client->irq) {
> reinit_completion(&data->completion);
>
> - ret = wait_for_completion_timeout(&data->completion, HZ/10);
> - if (ret < 0)
> - return ret;
> - else if (ret == 0)
> + time_left = wait_for_completion_timeout(&data->completion, HZ/10);
> + if (time_left == 0)
> return -ETIMEDOUT;
>
> vl53l0x_clear_irq(data);
prev parent reply other threads:[~2022-04-16 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 3:00 [PATCH] iio: proximity: Fix return value check of wait_for_completion_timeout Miaoqian Lin
2022-04-12 6:21 ` Sa, Nuno
2022-04-12 6:23 ` Sa, Nuno
2022-04-12 6:42 ` [PATCH v2] iio: proximity: vl53l0x: " Miaoqian Lin
2022-04-16 13:59 ` 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=20220416145906.1162767c@jic23-huawei \
--to=jic23@kernel.org \
--cc=drobyshevskyi@gmail.com \
--cc=lars@metafoo.de \
--cc=linmq006@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=songqiang1304521@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