From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Hans Verkuil <hansverk@cisco.com>,
Colin Ian King <colin.king@canonical.com>,
Markus Elfring <elfring@users.sourceforge.net>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [media] dvb-frontends: remove self assignments
Date: Fri, 22 Dec 2017 17:02:17 -0200 [thread overview]
Message-ID: <20171219110817.5979d60c@vento.lan> (raw)
In-Reply-To: <20171218171454.139245-1-ndesaulniers@google.com>
Em Mon, 18 Dec 2017 09:14:50 -0800
Nick Desaulniers <ndesaulniers@google.com> escreveu:
> These were leftover from:
> commit 469ffe083665 ("[media] tda18271c2dd: Remove the CHK_ERROR macro")
> and
> commit 58d5eaec9f87 ("[media] drxd: Don't use a macro for CHK_ERROR ...")
> that programmatically removed the CHK_ERROR macro, which left behind a
> few self assignments that Clang warns about. These instances aren't
> errors.
>
> Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
Thanks for the patch, but a similar one was already merged:
commit 2ddc125de832f4d8e1820dc923cb2029170beea0
Author: Colin Ian King <colin.king@canonical.com>
Date: Thu Nov 23 05:19:19 2017 -0500
media: dvb_frontend: remove redundant status self assignment
The assignment status to itself is redundant and can be removed.
Detected with Coccinelle.
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> ---
> drivers/media/dvb-frontends/drxd_hard.c | 3 ---
> drivers/media/dvb-frontends/tda18271c2dd.c | 1 -
> 2 files changed, 4 deletions(-)
>
> diff --git a/drivers/media/dvb-frontends/drxd_hard.c b/drivers/media/dvb-frontends/drxd_hard.c
> index 0696bc62dcc9..ff18a0f7dc41 100644
> --- a/drivers/media/dvb-frontends/drxd_hard.c
> +++ b/drivers/media/dvb-frontends/drxd_hard.c
> @@ -2140,7 +2140,6 @@ static int DRX_Start(struct drxd_state *state, s32 off)
> }
> break;
> }
> - status = status;
> if (status < 0)
> break;
>
> @@ -2251,7 +2250,6 @@ static int DRX_Start(struct drxd_state *state, s32 off)
> break;
>
> }
> - status = status;
> if (status < 0)
> break;
>
> @@ -2318,7 +2316,6 @@ static int DRX_Start(struct drxd_state *state, s32 off)
> }
> break;
> }
> - status = status;
> if (status < 0)
> break;
>
> diff --git a/drivers/media/dvb-frontends/tda18271c2dd.c b/drivers/media/dvb-frontends/tda18271c2dd.c
> index 2d2778be2d2f..45cd5ba0cf8a 100644
> --- a/drivers/media/dvb-frontends/tda18271c2dd.c
> +++ b/drivers/media/dvb-frontends/tda18271c2dd.c
> @@ -674,7 +674,6 @@ static int PowerScan(struct tda_state *state,
> Count = 200000;
> wait = true;
> }
> - status = status;
> if (status < 0)
> break;
> if (CID_Gain >= CID_Target) {
Thanks,
Mauro
prev parent reply other threads:[~2017-12-22 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 17:14 [PATCH] [media] dvb-frontends: remove self assignments Nick Desaulniers
2017-12-22 19:02 ` Mauro Carvalho Chehab [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=20171219110817.5979d60c@vento.lan \
--to=mchehab@kernel.org \
--cc=colin.king@canonical.com \
--cc=elfring@users.sourceforge.net \
--cc=hansverk@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).