From: Eduard Bostina <egbostina@gmail.com>
To: gregkh@linuxfoundation.org
Cc: broonie@kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, daniel.baluta@nxp.com,
simona.toaca@nxp.com, Eduard Bostina <egbostina@gmail.com>
Subject: [PATCH v2] staging: rtl8723bs: Clean up unnecessary parentheses and braces
Date: Wed, 4 Mar 2026 15:34:26 +0000 [thread overview]
Message-ID: <20260304153426.2217417-1-egbostina@gmail.com> (raw)
Increase code readability and follow Linux kernel coding style by
removing unnecessary parentheses and braces.
This also fixes the following checkpatch.pl issues:
WARNING: Unnecessary parentheses - maybe == should be = ?
WARNING: braces {} are not necessary for any arm of this statement
Signed-off-by: Eduard Bostina <egbostina@gmail.com>
---
drivers/staging/rtl8723bs/core/rtw_recv.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_recv.c b/drivers/staging/rtl8723bs/core/rtw_recv.c
index 1a52d3e1d285d..a1c2220ac476b 100644
--- a/drivers/staging/rtl8723bs/core/rtw_recv.c
+++ b/drivers/staging/rtl8723bs/core/rtw_recv.c
@@ -1339,11 +1339,10 @@ static signed int validate_recv_data_frame(struct adapter *adapter, union recv_f
}
- if (ret == _FAIL) {
+ if (ret == _FAIL)
goto exit;
- } else if (ret == RTW_RX_HANDLED) {
+ else if (ret == RTW_RX_HANDLED)
goto exit;
- }
if (!psta) {
@@ -1593,7 +1592,7 @@ static signed int wlanhdr_to_ethhdr(union recv_frame *precvframe)
eth_type = ntohs(be_tmp); /* pattrib->ether_type */
pattrib->eth_type = eth_type;
- if ((check_fwstate(pmlmepriv, WIFI_MP_STATE) == true)) {
+ if (check_fwstate(pmlmepriv, WIFI_MP_STATE) == true) {
ptr += rmv_len;
*ptr = 0x87;
*(ptr + 1) = 0x12;
--
2.43.0
next reply other threads:[~2026-03-04 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 15:34 Eduard Bostina [this message]
2026-03-04 15:44 ` [PATCH v2] staging: rtl8723bs: Clean up unnecessary parentheses and braces Greg KH
2026-03-04 15:53 ` Daniel Baluta
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=20260304153426.2217417-1-egbostina@gmail.com \
--to=egbostina@gmail.com \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=simona.toaca@nxp.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