From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: "Colin King" <colin.king@canonical.com>,
"Jacopo Mondi" <jacopo+renesas@jmondi.org>,
"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
linux-media@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] media: i2c: fix error check on max9286_read call
Date: Mon, 20 Jul 2020 20:04:35 +0100 [thread overview]
Message-ID: <ac2e793b-0f29-ac7b-d29f-3a4695c2eedc@ideasonboard.com> (raw)
In-Reply-To: <20200720161335.339174-1-colin.king@canonical.com>
Hi Colin,
On 20/07/2020 17:13, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Currently the error return from the call to max9286_read is masked
> with 0xf0 so the following check for a negative error return is
> never true. Fix this by checking for an error first, then masking
> the return value for subsequent conflink_mask checking.
Ooops!
> Addresses-Coverity: ("Logically dead code")
> fixes: 66d8c9d2422d ("media: i2c: Add MAX9286 driver")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Thanks,
Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> ---
> drivers/media/i2c/max9286.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/i2c/max9286.c b/drivers/media/i2c/max9286.c
> index 47f280518fdb..b364a3f60486 100644
> --- a/drivers/media/i2c/max9286.c
> +++ b/drivers/media/i2c/max9286.c
> @@ -405,10 +405,11 @@ static int max9286_check_config_link(struct max9286_priv *priv,
> * to 5 milliseconds.
> */
> for (i = 0; i < 10; i++) {
> - ret = max9286_read(priv, 0x49) & 0xf0;
> + ret = max9286_read(priv, 0x49);
> if (ret < 0)
> return -EIO;
>
> + ret &= 0xf0;
> if (ret == conflink_mask)
> break;
>
>
prev parent reply other threads:[~2020-07-20 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 16:13 Colin King
2020-07-20 19:04 ` Kieran Bingham [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=ac2e793b-0f29-ac7b-d29f-3a4695c2eedc@ideasonboard.com \
--to=kieran.bingham+renesas@ideasonboard.com \
--cc=colin.king@canonical.com \
--cc=jacopo+renesas@jmondi.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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®