From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Phillip Potter <phil@philpotter.co.uk>,
Larry.Finger@lwfinger.net, paskripkin@gmail.com,
straube.linux@gmail.com, martin@kaiser.cx,
abdun.nihaal@gmail.com, philipp.g.hortmann@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: r8188eu: convert rtw_pwr_wakeup to correct error code semantics
Date: Wed, 27 Jul 2022 14:47:28 +0200 [thread overview]
Message-ID: <YuEz4Edtp8J3Honj@kroah.com> (raw)
In-Reply-To: <20220727124342.GR2316@kadam>
On Wed, Jul 27, 2022 at 03:43:42PM +0300, Dan Carpenter wrote:
> On Wed, Jul 27, 2022 at 08:33:14AM +0200, Greg KH wrote:
> > > diff --git a/drivers/staging/r8188eu/core/rtw_pwrctrl.c b/drivers/staging/r8188eu/core/rtw_pwrctrl.c
> > > index cf9020a73933..8b1c50668dfe 100644
> > > --- a/drivers/staging/r8188eu/core/rtw_pwrctrl.c
> > > +++ b/drivers/staging/r8188eu/core/rtw_pwrctrl.c
> > > @@ -381,24 +381,24 @@ int rtw_pwr_wakeup(struct adapter *padapter)
> > > struct mlme_priv *pmlmepriv = &padapter->mlmepriv;
> > > unsigned long timeout = jiffies + msecs_to_jiffies(3000);
> > > unsigned long deny_time;
> > > - int ret = _SUCCESS;
> > > + int ret = 0;
> > >
> > > while (pwrpriv->ps_processing && time_before(jiffies, timeout))
> > > msleep(10);
> > >
> > > /* I think this should be check in IPS, LPS, autosuspend functions... */
> > > if (check_fwstate(pmlmepriv, _FW_LINKED)) {
> > > - ret = _SUCCESS;
> > > + ret = 0;
> >
> > Nit, you don't need to set this again, as you already set it above to 0.
> >
>
> I would sort of prefer to drop the initialization and keep this one.
Fine with me, either works.
greg k-h
prev parent reply other threads:[~2022-07-27 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 22:07 [PATCH v2] staging: r8188eu: convert rtw_pwr_wakeup to correct error code semantics Phillip Potter
2022-07-26 5:09 ` Philipp Hortmann
2022-07-26 13:35 ` Dan Carpenter
2022-07-26 15:46 ` Dan Carpenter
2022-07-26 22:14 ` Phillip Potter
2022-07-27 6:33 ` Greg KH
2022-07-27 12:43 ` Dan Carpenter
2022-07-27 12:47 ` Greg KH [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=YuEz4Edtp8J3Honj@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=abdun.nihaal@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
--cc=philipp.g.hortmann@gmail.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