From: osjin83@gmail.com
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
osjin83@gmail.com
Subject: [PATCH 2/3] staging: rtl8723bs: fix casting and alignment spacing in rtl8723b_phycfg.c
Date: Wed, 8 Apr 2026 19:32:07 +0900 [thread overview]
Message-ID: <20260408103208.7682-3-osjin83@gmail.com> (raw)
In-Reply-To: <20260408103208.7682-1-osjin83@gmail.com>
From: tas0dev <osjin83@gmail.com>
Clean up spacing issues related to type casting and function parameter
alignment as flagged by checkpatch.pl.
Specifically, this patch:
- Removes the unnecessary space between a type cast and the variable,
changing "(u8) value" to "(u8)value".
- Adjusts the alignment of arguments in function calls to match the
open parenthesis.
- Standardizes the formatting of multi-line function parameters for
better readability.
These changes are stylistic improvements and have no impact on the
runtime logic of the driver.
Signed-off-by: tas0dev <osjin83@gmail.com>
---
drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c b/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c
index cfa00775341b..498f7b25a2b5 100644
--- a/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c
+++ b/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c
@@ -395,7 +395,8 @@ int PHY_BBConfig8723B(struct adapter *Adapter)
PHY_SetRFReg(Adapter, RF_PATH_A, 0x1, 0xfffff, 0x780);
- rtw_write8(Adapter, REG_SYS_FUNC_EN, FEN_PPLL|FEN_PCIEA|FEN_DIO_PCIE|FEN_BB_GLB_RSTn|FEN_BBRSTB);
+ rtw_write8(Adapter, REG_SYS_FUNC_EN,
+ FEN_PPLL | FEN_PCIEA | FEN_DIO_PCIE | FEN_BB_GLB_RSTn | FEN_BBRSTB);
rtw_write8(Adapter, REG_AFE_XTAL_CTRL + 1, 0x80);
@@ -531,7 +532,7 @@ u8 PHY_GetTxPowerIndex(
struct hal_com_data *pHalData = GET_HAL_DATA(padapter);
s8 txPower = 0, powerDiffByRate = 0, limit = 0;
- txPower = (s8) PHY_GetTxPowerIndexBase(padapter, RFPath, Rate, BandWidth, Channel);
+ txPower = (s8)PHY_GetTxPowerIndexBase(padapter, RFPath, Rate, BandWidth, Channel);
powerDiffByRate = PHY_GetTxPowerByRate(padapter, RF_PATH_A, Rate);
limit = phy_get_tx_pwr_lmt(
@@ -551,7 +552,7 @@ u8 PHY_GetTxPowerIndex(
if (txPower > MAX_POWER_INDEX)
txPower = MAX_POWER_INDEX;
- return (u8) txPower;
+ return (u8)txPower;
}
void PHY_SetTxPowerLevel8723B(struct adapter *Adapter, u8 Channel)
--
2.53.0
next prev parent reply other threads:[~2026-04-08 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 10:32 [PATCH 0/3] staging: rtl8723bs: coding style cleanups for rtl8723b_phycfg.c osjin83
2026-04-08 10:32 ` [PATCH 1/3] staging: rtl8723bs: fix spacing around operators in rtl8723b_phycfg.c osjin83
2026-04-08 16:49 ` Luka Gejak
2026-04-08 10:32 ` osjin83 [this message]
2026-04-08 16:57 ` [PATCH 2/3] staging: rtl8723bs: fix casting and alignment spacing " Luka Gejak
2026-04-08 10:32 ` [PATCH 3/3] staging: rtl8723bs: remove unnecessary blank lines " osjin83
2026-04-08 16:58 ` Luka Gejak
2026-04-08 16:42 ` [PATCH 0/3] staging: rtl8723bs: coding style cleanups for rtl8723b_phycfg.c Luka Gejak
2026-04-08 17:00 ` Luka Gejak
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=20260408103208.7682-3-osjin83@gmail.com \
--to=osjin83@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