From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Surender Polsani <surenderpolsani@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Dan Carpenter <error27@gmail.com>
Subject: Re: [V4] staging : rtl8188eu : remove void function return
Date: Sun, 07 May 2017 23:27:44 -0700 [thread overview]
Message-ID: <1494224864.31950.56.camel@perches.com> (raw)
In-Reply-To: <20170508055913.GA18310@kroah.com>
On Mon, 2017-05-08 at 07:59 +0200, Greg KH wrote:
> On Mon, May 08, 2017 at 11:22:35AM +0530, Surender Polsani wrote:
> > kernel coding style doesn't allow the return statement
> > in void function.
> >
> > Signed-off-by: Surender Polsani <surenderpolsani@gmail.com>
> > ---
> > Changes for v2:
> > corrected subject line as suggested
> > Changes for v3:
> > modified from line as suggested by Greg KH
> > placed a semicolon in label for fixing build error
> > Changes for v4:
> > changes made as suggested by Dan Carpenter
No, Dan correctly suggested that the goto
and the label be removed, not what has been
done in this patch.
> > diff --git a/drivers/staging/rtl8188eu/hal/rtl8188e_dm.c b/drivers/staging/rtl8188eu/hal/rtl8188e_dm.c
[]
> > @@ -146,7 +146,6 @@ void rtw_hal_dm_watchdog(struct adapter *Adapter)
> >
> > if (!hw_init_completed)
> > goto skip_dm;
> > -
>
> Why did you remove this line?
I presume because of carelessness.
> > /* ODM */
> > pmlmepriv = &Adapter->mlmepriv;
> >
> > @@ -165,7 +164,7 @@ void rtw_hal_dm_watchdog(struct adapter *Adapter)
> > skip_dm:
> > /* Check GPIO to determine current RF on/off and Pbc status. */
> > /* Check Hardware Radio ON/OFF or not */
> > - return;
> > + ;
>
> Why is the ';' still here?
A label immediately before a function termination
requires a statement after the label and before the
last closing brace.
prev parent reply other threads:[~2017-05-08 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 5:52 [V4] staging : rtl8188eu : remove void function return Surender Polsani
2017-05-08 5:59 ` Greg KH
2017-05-08 6:27 ` Joe Perches [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=1494224864.31950.56.camel@perches.com \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=surenderpolsani@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