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 v2 3/4] staging: rtl8723bs: wrap long lines in rtl8723b_phycfg.c
Date: Thu, 9 Apr 2026 14:04:51 +0900 [thread overview]
Message-ID: <20260409050452.97774-4-osjin83@gmail.com> (raw)
In-Reply-To: <20260409050452.97774-1-osjin83@gmail.com>
From: Jinemon Tama <osjin83@gmail.com>
Wrap lines that exceed the 100-column limit in rtl8723b_phycfg.c to
resolve checkpatch.pl warnings. Arguments are aligned with the open
parenthesis where appropriate to maintain readability.
Signed-off-by: Jinemon Tama <osjin83@gmail.com>
---
drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c b/drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c
index 01e1595fb46f..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);
--
2.53.0
next prev parent reply other threads:[~2026-04-09 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 5:04 [PATCH v2 0/4] staging: rtl8723bs: coding style cleanups for rtl8723b_phycfg.c osjin83
2026-04-09 5:04 ` [PATCH v2 1/4] staging: rtl8723bs: fix spacing around operators in rtl8723b_phycfg.c osjin83
2026-04-09 5:04 ` [PATCH v2 2/4] staging: rtl8723bs: remove space after type cast osjin83
2026-04-09 5:04 ` osjin83 [this message]
2026-04-09 5:04 ` [PATCH v2 4/4] staging: rtl8723bs: remove unnecessary blank lines in rtl8723b_phycfg.c osjin83
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=20260409050452.97774-4-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