From: Moksh Panicker <mokshpanicker.7@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Moksh Panicker <mokshpanicker.7@gmail.com>
Subject: [PATCH v2] staging: rtl8723bs: Remove unnecessary braces in rtl8723bs_xmit.c
Date: Sun, 3 May 2026 08:25:15 +0000 [thread overview]
Message-ID: <20260503082515.8279-1-mokshpanicker.7@gmail.com> (raw)
In-Reply-To: <2026050326-photo-untamed-82cb@gregkh>
Braces are not necessary for single statement blocks.
This fixes the following checkpatch.pl warning:
WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: Moksh Panicker <mokshpanicker.7@gmail.com>
---
v2: Added description of the change to the patch body.
---
drivers/staging/rtl8723bs/hal/hal_btcoex.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/rtl8723bs/hal/hal_btcoex.c b/drivers/staging/rtl8723bs/hal/hal_btcoex.c
index 2a2dd60be8bb..aab68aa299c8 100644
--- a/drivers/staging/rtl8723bs/hal/hal_btcoex.c
+++ b/drivers/staging/rtl8723bs/hal/hal_btcoex.c
@@ -402,9 +402,6 @@ static u8 halbtcoutsrc_Get(void *pBtcContext, u8 getType, void *pOutBuf)
case BTC_GET_U1_MAC_PHY_MODE:
*pu8 = BTC_SMSP;
-/* *pU1Tmp = BTC_DMSP; */
-/* *pU1Tmp = BTC_DMDP; */
-/* *pU1Tmp = BTC_MP_UNKNOWN; */
break;
case BTC_GET_U1_AP_NUM:
--
2.34.1
next prev parent reply other threads:[~2026-05-03 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 21:56 [PATCH] staging: rtl8723bs: Remove unnecessary braces in rtl8723bs_xmit.c Moksh Panicker
2026-05-03 6:02 ` Greg KH
2026-05-03 7:59 ` [PATCH v2] " Moksh Panicker
2026-05-03 8:18 ` Greg KH
2026-05-03 8:25 ` Moksh Panicker [this message]
2026-05-03 8:32 ` Moksh Panicker
2026-05-03 9:00 ` Greg KH
2026-05-03 9:51 ` Moksh Panicker
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=20260503082515.8279-1-mokshpanicker.7@gmail.com \
--to=mokshpanicker.7@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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