From: Dan Carpenter <dan.carpenter@oracle.com>
To: Colin King <colin.king@canonical.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: dvb: redundant assignment to variable tmp
Date: Tue, 27 Aug 2019 16:10:33 +0300 [thread overview]
Message-ID: <20190827131033.GD23584@kadam> (raw)
In-Reply-To: <20190827111527.26337-1-colin.king@canonical.com>
On Tue, Aug 27, 2019 at 12:15:27PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Variable tmp is being assigned a value that is never read and tmp
> is being re-assigned a little later on. The assignment is redundant
> and hence can be removed.
>
> Addresses-Coverity: ("Ununsed value")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/media/dvb-frontends/sp8870.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/media/dvb-frontends/sp8870.c b/drivers/media/dvb-frontends/sp8870.c
> index 655db8272268..f6793c9c2dc3 100644
> --- a/drivers/media/dvb-frontends/sp8870.c
> +++ b/drivers/media/dvb-frontends/sp8870.c
> @@ -378,8 +378,6 @@ static int sp8870_read_ber (struct dvb_frontend* fe, u32 * ber)
> if (ret < 0)
> return -EIO;
>
> - tmp = ret & 0x3F;
> -
This is pre git code. It's not clear if the tmp is supposed to be used
or if we can remove the sp8870_readreg() call also... The problem is
that we're disabling the warning without necessarily writing the best
fix. It's better to leave the warning there until we are more sure of
the correct fix. The warning has useful information and it's not
hurting anyone.
regards,
dan carpenter
prev parent reply other threads:[~2019-08-27 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 11:15 [PATCH] media: dvb: redundant assignment to variable tmp Colin King
2019-08-27 13:10 ` Dan Carpenter [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=20190827131033.GD23584@kadam \
--to=dan.carpenter@oracle.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).