mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Saurav Girepunje <saurav.girepunje@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
	straube.linux@gmail.com, martin@kaiser.cx,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	saurav.girepunje@hotmail.com
Subject: Re: [PATCH] staging: r8188eu: hal: else is not useful after a return
Date: Tue, 2 Nov 2021 00:53:33 +0530	[thread overview]
Message-ID: <5013033b-b1f1-aef7-9fb8-a8431e83960b@gmail.com> (raw)
In-Reply-To: <YX/lRMNGsCZMKAV3@kroah.com>



On 01/11/21 6:31 pm, Greg KH wrote:
> On Mon, Nov 01, 2021 at 12:05:50AM +0530, Saurav Girepunje wrote:
>> In the function rtl8188eu_hal_init() else after the return statement
>> of the if section is not useful. As if condition is true function will
>> return from if section, On the other case if condition is false
>> function will not return and statement after the if section will
>> execute, So there is no need to have else in this case. Remove the
>> else after a return statement of the if section.
>>
>> Signed-off-by: Saurav Girepunje <saurav.girepunje@gmail.com>
>> ---
>>  drivers/staging/r8188eu/hal/usb_halinit.c | 7 ++++---
>>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> 
> Hi,
> 
> This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
> a patch that has triggered this response.  He used to manually respond
> to these common problems, but in order to save his sanity (he kept
> writing the same thing over and over, yet to different people), I was
> created.  Hopefully you will not take offence and will fix the problem
> in your patch and resubmit it so that it can be accepted into the Linux
> kernel tree.
> 
> You are receiving this message because of the following common error(s)
> as indicated below:
> 
> - You sent multiple patches, yet no indication of which ones should be
>   applied in which order.  Greg could just guess, but if you are
>   receiving this email, he guessed wrong and the patches didn't apply.
>   Please read the section entitled "The canonical patch format" in the
>   kernel file, Documentation/SubmittingPatches for a description of how
>   to do this so that Greg has a chance to apply these correctly.
> 
> If you wish to discuss this problem further, or you have questions about
> how to resolve this issue, please feel free to respond to this email and
> Greg will reply once he has dug out from the pending patches received
> from other developers.
> 
> thanks,
> 
> greg k-h's patch email bot>

Hi Greg,

I have send only one patch for usb_halinit.c.
However I have send another patch staging: r8188eu: hal: break after the return not useful
for another file HalPwrSeqCmd.c both are on same path drivers/staging/r8188eu/hal/ 

Regards,
Saurav
 

  reply	other threads:[~2021-11-01 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-31 18:35 Saurav Girepunje
2021-11-01 13:01 ` Greg KH
2021-11-01 19:23   ` Saurav Girepunje [this message]
2021-11-05  8:28     ` 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=5013033b-b1f1-aef7-9fb8-a8431e83960b@gmail.com \
    --to=saurav.girepunje@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=martin@kaiser.cx \
    --cc=phil@philpotter.co.uk \
    --cc=saurav.girepunje@hotmail.com \
    --cc=straube.linux@gmail.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®