From: Marcos Antonio de Jesus Filho <mdejesusfilho@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Forest Bond <forest@alittletooquiet.net>,
outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] staging: vt6655: Remove useless else
Date: Thu, 29 Oct 2020 23:12:29 -0700 [thread overview]
Message-ID: <20201030061229.GA89419@Zangetsu> (raw)
In-Reply-To: <20201029080924.GA2011@Zangetsu>
On Thu, Oct 29, 2020 at 01:09:45AM -0700, Marcos Antonio de Jesus Filho wrote:
> On Thu, Oct 29, 2020 at 08:07:23AM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Oct 28, 2020 at 11:59:58PM -0700, Marcos Antonio de Jesus Filho wrote:
> > > The else statement is not useful due to the presence of a return
> > > statement on the if block. Remove the else statement and adjust the
> > > indentation of the code. Reported by checkpatch.
> > >
> > > Signed-off-by: Marcos Antonio de Jesus Filho <mdejesusfilho@gmail.com>
> > > ---
> > > drivers/staging/vt6655/rxtx.c | 36 +++++++++++++++++------------------
> > > 1 file changed, 18 insertions(+), 18 deletions(-)
> > >
> > > diff --git a/drivers/staging/vt6655/rxtx.c b/drivers/staging/vt6655/rxtx.c
> > > index 477d19314634..978efe81077a 100644
> > > --- a/drivers/staging/vt6655/rxtx.c
> > > +++ b/drivers/staging/vt6655/rxtx.c
> > > @@ -519,28 +519,28 @@ s_uFillDataHead(
> > > wCurrentRate, bNeedAck, uFragIdx, cbLastFragmentSize, uMACfragNum, byFBOption));
> > > buf->time_stamp_off = vnt_time_stamp_off(pDevice, wCurrentRate);
> > > return buf->duration;
> > > - } else {
> > > - struct vnt_tx_datahead_ab *buf = pTxDataHead;
> > > - /* Get SignalField, ServiceField & Length */
> > > - vnt_get_phy_field(pDevice, cbFrameLength, wCurrentRate,
> > > - byPktType, &buf->ab);
> > > + }
> > >
> > > - if (is_pspoll) {
> > > - __le16 dur = cpu_to_le16(pDevice->current_aid | BIT(14) | BIT(15));
> > > + struct vnt_tx_datahead_ab *buf = pTxDataHead;
> > > + /* Get SignalField, ServiceField & Length */
> > > + vnt_get_phy_field(pDevice, cbFrameLength, wCurrentRate,
> > > + byPktType, &buf->ab);
> > >
> > > - buf->duration = dur;
> > > - } else {
> > > - /* Get Duration and TimeStampOff */
> > > - buf->duration =
> > > - cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A, cbFrameLength, byPktType,
> > > - wCurrentRate, bNeedAck, uFragIdx,
> > > - cbLastFragmentSize, uMACfragNum,
> > > - byFBOption));
> > > - }
> > > + if (is_pspoll) {
> > > + __le16 dur = cpu_to_le16(pDevice->current_aid | BIT(14) | BIT(15));
> > >
> > > - buf->time_stamp_off = vnt_time_stamp_off(pDevice, wCurrentRate);
> > > - return buf->duration;
> > > + buf->duration = dur;
> > > + } else {
> > > + /* Get Duration and TimeStampOff */
> > > + buf->duration =
> > > + cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A, cbFrameLength, byPktType,
> > > + wCurrentRate, bNeedAck, uFragIdx,
> > > + cbLastFragmentSize, uMACfragNum,
> > > + byFBOption));
> > > }
> > > +
> > > + buf->time_stamp_off = vnt_time_stamp_off(pDevice, wCurrentRate);
> > > + return buf->duration;
> > > } else {
> >
> > You do the same thing here, right? Shouldn't this else be dropped?
>
> Definitely. I did not do it because we are instructed to solve one 'Warning' at time. I was going to do it in another patch.
> Should I edit this patch and fix it now?
>
> >
> > thanks,
> >
> > greg k-h
I notice that after removing the else statement I get the compilation error "ISO C90 forbids mixed declarations and code", because we eliminate the scope of the else block. Should I leave as it is?
next prev parent reply other threads:[~2020-10-30 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 6:59 [PATCH] staging: vt6655: Remove useless else Marcos Antonio de Jesus Filho
2020-10-29 7:07 ` Greg Kroah-Hartman
2020-10-29 8:09 ` Marcos Antonio de Jesus Filho
2020-10-30 6:12 ` Marcos Antonio de Jesus Filho [this message]
2020-10-30 7:12 ` Greg Kroah-Hartman
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=20201030061229.GA89419@Zangetsu \
--to=mdejesusfilho@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.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 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.