From: Rebecca Mckeever <remckee0@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: r8188eu: fix suspect code indent for conditional statements
Date: Thu, 31 Mar 2022 07:06:00 -0500 [thread overview]
Message-ID: <YkWZKOvThq5paUi3@bertie> (raw)
In-Reply-To: <20220330062829.GF3293@kadam>
Hi Dan,
On Wed, Mar 30, 2022 at 09:28:29AM +0300, Dan Carpenter wrote:
> I don't really like the focus on commit message minutia... :/
> Basically everyone can understand the commit message. There are one or
> two maintainers who will fly into a rage when they see the word "fix"
> in a commit message but I have a simple solution where I just never
> email them again. My time is too valuable for that nonsense.
>
> We would have applied this patch as is. Or I would normally have
> written it like this:
>
> [PATCH] staging: r8188eu: Delete a stray tab in rtw_survey_cmd_callback()
>
> This code works fine, but the line is indented too far so it's confusing.
> Delete a tab.
>
> Signed-off-by: ...
>
> I had reviewed this patch earlier and almost pointed out that both sides
> of the if statement are the same except for the comment. The "need to
> make timeout handlerOS independent" comment is wrong. I have not looked
> at the details of the other comment.
>
> I did not send my review comments because the patch was fine. But what
> we want is for the code to look more like this.
>
> regards,
> dan carpenter
>
> diff --git a/drivers/staging/r8188eu/core/rtw_cmd.c b/drivers/staging/r8188eu/core/rtw_cmd.c
> index 6eca30124ee8..dcf7b24f95a8 100644
> --- a/drivers/staging/r8188eu/core/rtw_cmd.c
> +++ b/drivers/staging/r8188eu/core/rtw_cmd.c
> @@ -1404,11 +1404,8 @@ void rtw_survey_cmd_callback(struct adapter *padapter, struct cmd_obj *pcmd)
> {
> struct mlme_priv *pmlmepriv = &padapter->mlmepriv;
>
> - if (pcmd->res == H2C_DROPPED) {
> + if (pcmd->res != H2C_SUCCESS) {
> /* TODO: cancel timer and do timeout handler directly... */
> - /* need to make timeout handlerOS independent */
> - _set_timer(&pmlmepriv->scan_to_timer, 1);
> - } else if (pcmd->res != H2C_SUCCESS) {
> _set_timer(&pmlmepriv->scan_to_timer, 1);
> }
>
Is it okay if I submit a patch to implement your suggestion? I would
include a "Suggested-by" tag.
Thanks,
Rebecca
next prev parent reply other threads:[~2022-03-31 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 7:53 [PATCH] staging: r8188eu: fix suspect code indent for conditional statements Rebecca Mckeever
2022-03-29 16:16 ` Alison Schofield
2022-03-30 0:48 ` Rebecca Mckeever
2022-03-30 1:09 ` Alison Schofield
2022-03-30 6:28 ` Dan Carpenter
2022-03-31 12:06 ` Rebecca Mckeever [this message]
2022-03-31 12:21 ` Dan Carpenter
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=YkWZKOvThq5paUi3@bertie \
--to=remckee0@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=alison.schofield@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=phil@philpotter.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).