mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mukesh Ojha <mojha@codeaurora.org>
To: Colin King <colin.king@canonical.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Aditya Pakki <pakki001@umn.edu>, Sean Young <sean@mess.org>,
	linux-media@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: dvb: clean up redundant break statements
Date: Sat, 30 Mar 2019 23:44:52 +0530	[thread overview]
Message-ID: <7392df5f-af02-18aa-beb8-36052f52a170@codeaurora.org> (raw)
In-Reply-To: <20190330152503.9923-1-colin.king@canonical.com>


On 3/30/2019 8:55 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There are several places where a break statement occurs before
> a following break statement; these are unnecessary and can be
> removed to clean up the code a little.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>

Cheers,
-Mukesh


> ---
>   drivers/media/dvb-frontends/drxd_hard.c | 30 +++++--------------------
>   1 file changed, 5 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/media/dvb-frontends/drxd_hard.c b/drivers/media/dvb-frontends/drxd_hard.c
> index 0a5b15bee1d7..c597d6fc3046 100644
> --- a/drivers/media/dvb-frontends/drxd_hard.c
> +++ b/drivers/media/dvb-frontends/drxd_hard.c
> @@ -2263,61 +2263,41 @@ static int DRX_Start(struct drxd_state *state, s32 off)
>   		case DRX_CHANNEL_LOW:
>   			transmissionParams |= SC_RA_RAM_OP_PARAM_PRIO_LO;
>   			status = Write16(state, EC_SB_REG_PRIOR__A, EC_SB_REG_PRIOR_LO, 0x0000);
> -			if (status < 0)
> -				break;
>   			break;
>   		case DRX_CHANNEL_HIGH:
>   			transmissionParams |= SC_RA_RAM_OP_PARAM_PRIO_HI;
>   			status = Write16(state, EC_SB_REG_PRIOR__A, EC_SB_REG_PRIOR_HI, 0x0000);
> -			if (status < 0)
> -				break;
>   			break;
> -
>   		}
>   
>   		switch (p->code_rate_HP) {
>   		case FEC_1_2:
>   			transmissionParams |= SC_RA_RAM_OP_PARAM_RATE_1_2;
> -			if (state->type_A) {
> +			if (state->type_A)
>   				status = Write16(state, EC_VD_REG_SET_CODERATE__A, EC_VD_REG_SET_CODERATE_C1_2, 0x0000);
> -				if (status < 0)
> -					break;
> -			}
>   			break;
>   		default:
>   			operationMode |= SC_RA_RAM_OP_AUTO_RATE__M;
>   			/* fall through */
>   		case FEC_2_3:
>   			transmissionParams |= SC_RA_RAM_OP_PARAM_RATE_2_3;
> -			if (state->type_A) {
> +			if (state->type_A)
>   				status = Write16(state, EC_VD_REG_SET_CODERATE__A, EC_VD_REG_SET_CODERATE_C2_3, 0x0000);
> -				if (status < 0)
> -					break;
> -			}
>   			break;
>   		case FEC_3_4:
>   			transmissionParams |= SC_RA_RAM_OP_PARAM_RATE_3_4;
> -			if (state->type_A) {
> +			if (state->type_A)
>   				status = Write16(state, EC_VD_REG_SET_CODERATE__A, EC_VD_REG_SET_CODERATE_C3_4, 0x0000);
> -				if (status < 0)
> -					break;
> -			}
>   			break;
>   		case FEC_5_6:
>   			transmissionParams |= SC_RA_RAM_OP_PARAM_RATE_5_6;
> -			if (state->type_A) {
> +			if (state->type_A)
>   				status = Write16(state, EC_VD_REG_SET_CODERATE__A, EC_VD_REG_SET_CODERATE_C5_6, 0x0000);
> -				if (status < 0)
> -					break;
> -			}
>   			break;
>   		case FEC_7_8:
>   			transmissionParams |= SC_RA_RAM_OP_PARAM_RATE_7_8;
> -			if (state->type_A) {
> +			if (state->type_A)
>   				status = Write16(state, EC_VD_REG_SET_CODERATE__A, EC_VD_REG_SET_CODERATE_C7_8, 0x0000);
> -				if (status < 0)
> -					break;
> -			}
>   			break;
>   		}
>   		if (status < 0)

      reply	other threads:[~2019-03-30 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-30 15:25 Colin King
2019-03-30 18:14 ` Mukesh Ojha [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=7392df5f-af02-18aa-beb8-36052f52a170@codeaurora.org \
    --to=mojha@codeaurora.org \
    --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 \
    --cc=pakki001@umn.edu \
    --cc=sean@mess.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

all inboxes | Powered by JetHome®