From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: jiwonaid0@gmail.com, gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] staging: rtl8723bs: Delete unnecessary braces for single statement blocks
Date: Fri, 2 Aug 2024 07:45:47 +0200 [thread overview]
Message-ID: <e4308685-bfd1-4795-bcc4-d2a246dae0c1@gmail.com> (raw)
In-Reply-To: <20240801155138.25531-1-jiwonaid0@gmail.com>
On 8/1/24 17:51, jiwonaid0@gmail.com wrote:
> From: Jiwon Kim <jiwonaid0@gmail.com>
please omit the previous line as it is not required.
>
> Deleted braces {} for single statement blocks.
>
> Addressed scripts/checkpatch.pl warning.
>
Please do not add extra empty lines in the description when not
required. Consider that we have a lot of commits and it is most wanted
that the description is short.
It is not required to add the name of the tool who found this, but it
can be named. Much more important is a good description why this change
makes sense...
For example:
... to shorten code.
... to improve readability.
Use present in the description. So Deleted should be Delete.
> Signed-off-by: Jiwon Kim <jiwonaid0@gmail.com>
> ---
> drivers/staging/rtl8723bs/os_dep/xmit_linux.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/os_dep/xmit_linux.c b/drivers/staging/rtl8723bs/os_dep/xmit_linux.c
> index 1eeabfffd6d2..e0736707a211 100644
> --- a/drivers/staging/rtl8723bs/os_dep/xmit_linux.c
> +++ b/drivers/staging/rtl8723bs/os_dep/xmit_linux.c
> @@ -144,9 +144,8 @@ static int rtw_mlcst2unicst(struct adapter *padapter, struct sk_buff *skb)
> psta = list_entry(plist, struct sta_info, asoc_list);
>
> stainfo_offset = rtw_stainfo_offset(pstapriv, psta);
> - if (stainfo_offset_valid(stainfo_offset)) {
> + if (stainfo_offset_valid(stainfo_offset))
> chk_alive_list[chk_alive_num++] = stainfo_offset;
> - }
> }
> spin_unlock_bh(&pstapriv->asoc_list_lock);
>
Hi Jiwon,
please consider the above comments.
Please make your "Subject" line more unique. Consider that we may end up
with having dozen of commits like yours, all of them referring to
different removals and all without the necessary information to tell
what they differ in (except the driver/subsystem). So it would help if
you add the changed file or function to make it more unique.
If you send in a second version of this patch please use a change
history. Description from Dan under:
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
Thanks for your support.
Bye Philipp
prev parent reply other threads:[~2024-08-02 5:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 15:51 [PATCH net-next] staging: rtl8723bs: Delete unnecessary braces for single statement blocks jiwonaid0
2024-08-02 5:45 ` Philipp Hortmann [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=e4308685-bfd1-4795-bcc4-d2a246dae0c1@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiwonaid0@gmail.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