From: Dan Carpenter <dan.carpenter@oracle.com>
To: Fabio Aiuto <fabioaiuto83@gmail.com>
Cc: Bryan Brattlof <hello@bryanbrattlof.com>,
Hans de Goede <hdegoede@redhat.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: remove if (true) statement
Date: Wed, 19 May 2021 16:31:08 +0300 [thread overview]
Message-ID: <20210519133108.GW1955@kadam> (raw)
In-Reply-To: <20210519132529.GV1955@kadam>
On Wed, May 19, 2021 at 04:25:29PM +0300, Dan Carpenter wrote:
> On Wed, May 19, 2021 at 02:44:38PM +0200, Fabio Aiuto wrote:
> > Hi Bryan,
> >
> > On Tue, May 18, 2021 at 02:45:19PM +0000, Bryan Brattlof wrote:
> > > 'if (true) { ... }' will always evaluate to true. Remove it and
> > > save a few tabs for somewhere else.
> > >
> > > Signed-off-by: Bryan Brattlof <hello@bryanbrattlof.com>
> > > ---
> > > drivers/staging/rtl8723bs/core/rtw_ap.c | 159 ++++++++++++------------
> > > 1 file changed, 78 insertions(+), 81 deletions(-)
> > >
> > > diff --git a/drivers/staging/rtl8723bs/core/rtw_ap.c b/drivers/staging/rtl8723bs/core/rtw_ap.c
> > > index 9df4476b2e2d..98b1bec67999 100644
> > > --- a/drivers/staging/rtl8723bs/core/rtw_ap.c
> > > +++ b/drivers/staging/rtl8723bs/core/rtw_ap.c
> > > @@ -59,112 +59,109 @@ static void update_BCNTIM(struct adapter *padapter)
> > >
> >
> > I was wondering why are you using the first patch of a nine patch
> > series as a 'cover letter' of an eight patch patchset.
> >
> > In other words, why putting the In-Reply-To field of all patches subsequent
> > to the first one ponting to the first patch itself as a cover letter,
> > is it a recommened practice?
>
> It's fine. It doesn't matter. It's not recommended. I do it normally
> if I have to send patches in certain order. I never write cover letters
> because my patches are all independent bug fixes and not new features.
Wait, this was just a mistake I think. It's not a cover letter. It's
not part of the eight patch series but it probably was intended to be as
you suggest.
The patches are basically okay. Greg applies patches in the order that
he recieves them so it should all apply fine. And if it doesn't Greg
will just ask for a resend. No big deal.
regards,
dan carpenter
next prev parent reply other threads:[~2021-05-19 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 14:45 [PATCH] staging: rtl8723bs: remove if (true) statement Bryan Brattlof
2021-05-19 12:44 ` Fabio Aiuto
2021-05-19 13:25 ` Dan Carpenter
2021-05-19 13:31 ` Dan Carpenter [this message]
2021-05-19 13:51 ` Bryan Brattlof
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=20210519133108.GW1955@kadam \
--to=dan.carpenter@oracle.com \
--cc=Larry.Finger@lwfinger.net \
--cc=fabioaiuto83@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=hello@bryanbrattlof.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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