mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] staging: rtlwifi: Remove nonessential semicolon
Date: Sat, 3 Mar 2018 20:30:19 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1803032029530.9544@hadrien> (raw)
In-Reply-To: <20180303190913.GA4555@seema-Inspiron-15-3567>



On Sun, 4 Mar 2018, Arushi Singhal wrote:

> Remove non-essential semicolon after 'else' and 'switch' statements. Issue
> found using semicolon.cocci Coccinelle script.
>
> Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>

Acked-by: Julia Lawall <julia.lawall@lip6.fr>

It seems strange that someone would write code like that...

julia

> ---
>  drivers/staging/rtlwifi/base.c               | 6 +++---
>  drivers/staging/rtlwifi/phydm/phydm_rainfo.c | 1 -
>  2 files changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/rtlwifi/base.c b/drivers/staging/rtlwifi/base.c
> index c947def..eea0003 100644
> --- a/drivers/staging/rtlwifi/base.c
> +++ b/drivers/staging/rtlwifi/base.c
> @@ -710,20 +710,20 @@ u8 rtl_mrate_idx_to_arfr_id(
>  			ret = RATEID_IDX_BGN_40M_1SS;
>  		else
>  			ret = RATEID_IDX_BGN_40M_2SS;
> -		; break;
> +		break;
>  	case RATR_INX_WIRELESS_N:
>  	case RATR_INX_WIRELESS_NG:
>  		if (rtlphy->rf_type == RF_1T1R)
>  			ret = RATEID_IDX_GN_N1SS;
>  		else
>  			ret = RATEID_IDX_GN_N2SS;
> -		; break;
> +		break;
>  	case RATR_INX_WIRELESS_NB:
>  		if (rtlphy->rf_type == RF_1T1R)
>  			ret = RATEID_IDX_BGN_20M_1SS_BN;
>  		else
>  			ret = RATEID_IDX_BGN_20M_2SS_BN;
> -		; break;
> +		break;
>  	case RATR_INX_WIRELESS_GB:
>  		ret = RATEID_IDX_BG;
>  		break;
> diff --git a/drivers/staging/rtlwifi/phydm/phydm_rainfo.c b/drivers/staging/rtlwifi/phydm/phydm_rainfo.c
> index 8c08c76..e10a91a 100644
> --- a/drivers/staging/rtlwifi/phydm/phydm_rainfo.c
> +++ b/drivers/staging/rtlwifi/phydm/phydm_rainfo.c
> @@ -142,7 +142,6 @@ void odm_c2h_ra_para_report_handler(void *dm_void, u8 *cmd_buf, u8 cmd_len)
>  				     "SGI_support =", cmd_buf[7]);
>  			ODM_RT_TRACE(dm, ODM_FW_DEBUG_TRACE, "%5s  %d\n",
>  				     "Rate_ID =", cmd_buf[8]);
> -			;
>  		}
>  		ODM_RT_TRACE(dm, ODM_FW_DEBUG_TRACE,
>  			     "-------------------------------\n");
> --
> 2.7.4
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20180303190913.GA4555%40seema-Inspiron-15-3567.
> For more options, visit https://groups.google.com/d/optout.
>

      reply	other threads:[~2018-03-03 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03 19:09 Arushi Singhal
2018-03-03 19:30 ` Julia Lawall [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=alpine.DEB.2.20.1803032029530.9544@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=arushisinghal19971997@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=outreachy-kernel@googlegroups.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

all inboxes | Powered by JetHome®