All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>,
	 outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] Staging: rtl8192u: Remove brake statement
Date: Fri, 20 Feb 2015 06:28:48 -0500	[thread overview]
Message-ID: <54E71A70.5010308@gmail.com> (raw)
In-Reply-To: <1424384019-21836-1-git-send-email-ksenija.stanojevic@gmail.com>

On 02/19/15 17:13, Ksenija Stanojevic wrote:
> This patch fixes the checkpatch.pl warning:
> WARNING: "break is not useful after a goto or return"
> 
> Signed-off-by: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
> ---
>  drivers/staging/rtl8192u/r819xU_phy.c | 1 -
>  1 file changed, 1 deletion(-)

Patch looks good - your patch description works, so this is in the minor
section.

However, in general I recommend writing a message rather than relying on
automated output from checkpatch. You can note in the message that the
issue was found by checkpatch if you like. Something like this:

"Remove meaningless break after return in switch statement. This was
found by checkpatch.pl."

Cheers,
Jes


> diff --git a/drivers/staging/rtl8192u/r819xU_phy.c b/drivers/staging/rtl8192u/r819xU_phy.c
> index dbd3321..d006602 100644
> --- a/drivers/staging/rtl8192u/r819xU_phy.c
> +++ b/drivers/staging/rtl8192u/r819xU_phy.c
> @@ -1344,7 +1344,6 @@ static u8 rtl8192_phy_SwChnlStepByStep(struct net_device *dev, u8 channel,
>  	default:
>  		RT_TRACE(COMP_ERR, "Unknown RFChipID: %d\n", priv->rf_chip);
>  		return true;
> -		break;
>  	}
>  
>  
> 



  reply	other threads:[~2015-02-20 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 22:13 [PATCH] Staging: rtl8192u: Remove brake statement Ksenija Stanojevic
2015-02-20 11:28 ` Jes Sorensen [this message]
2015-02-26 21:21 ` [Outreachy kernel] " Greg KH

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=54E71A70.5010308@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=ksenija.stanojevic@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.