From: Igor Putko <igorpetindev@gmail.com>
To: Dan Carpenter <error27@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Igor Putko <igorpetindev@gmail.com>
Subject: [PATCH 1/3] staging: rtl8723bs: remove empty loop and stale comment in HalPhyRf.c
Date: Mon, 25 May 2026 15:10:02 +0300 [thread overview]
Message-ID: <20260525121004.4989-1-igorpetindev@gmail.com> (raw)
In-Reply-To: <ahPw0yB7Ax3lfhKu@stanley.mountain>
The 'for' loop in ODM_TXPowerTrackingCallback_ThermalMeter performs no
operations and just iterates over the path count. This is unnecessary code.
Also, remove the associated "Print Swing base & current" comment, as
it no longer refers to any active code.
Signed-off-by: Igor Putko <igorpetindev@gmail.com>
---
drivers/staging/rtl8723bs/hal/HalPhyRf.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/staging/rtl8723bs/hal/HalPhyRf.c b/drivers/staging/rtl8723bs/hal/HalPhyRf.c
index 7bef05a9a..f67b8d70b 100644
--- a/drivers/staging/rtl8723bs/hal/HalPhyRf.c
+++ b/drivers/staging/rtl8723bs/hal/HalPhyRf.c
@@ -234,10 +234,6 @@ void ODM_TXPowerTrackingCallback_ThermalMeter(struct adapter *Adapter)
pDM_Odm->RFCalibrateInfo.PowerIndexOffset[p] = 0;
}
- /* Print Swing base & current */
- for (p = RF_PATH_A; p < c.RfPathCount; p++) {
- }
-
if (
(pDM_Odm->RFCalibrateInfo.PowerIndexOffset[RF_PATH_A] != 0 ||
pDM_Odm->RFCalibrateInfo.PowerIndexOffset[RF_PATH_B] != 0) &&
--
2.34.1
next prev parent reply other threads:[~2026-05-25 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 17:52 [PATCH] staging: rtl8723bs: remove unnecessary braces and fix indentation in HalPhyRf.c Igor Putko
2026-05-25 6:48 ` Dan Carpenter
2026-05-25 12:10 ` Igor Putko [this message]
2026-05-25 12:10 ` [PATCH 2/3] staging: rtl8723bs: fix coding style for PowerIndexOffset initialization Igor Putko
2026-05-25 12:10 ` [PATCH 3/3] staging: rtl8723bs: fix coding style for TxPwrTrackSetPwr calls Igor Putko
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=20260525121004.4989-1-igorpetindev@gmail.com \
--to=igorpetindev@gmail.com \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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