Linux kernel staging patches
 help / color / mirror / Atom feed
From: Thomas Prud'homme <t+linux@prudhomme.li>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, Thomas Prud'homme <t+linux@prudhomme.li>
Subject: [PATCH] staging: rtl8723bs: fix lines over 100 characters in hal_intf.c
Date: Wed,  9 Sep 2026 19:41:52 +0200	[thread overview]
Message-ID: <20260909174152.16934-1-t+linux@prudhomme.li> (raw)

Wrap the parameter list of rtw_hal_set_odm_var() across two lines,
and move the comment on the rtl8723b_HalDmWatchDog_in_LPS() call
above the call instead of trailing it, so both lines fit within the
checkpatch.pl line length limit. No functional change.

Signed-off-by: Thomas Prud'homme <t+linux@prudhomme.li>
---
 drivers/staging/rtl8723bs/hal/hal_intf.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/rtl8723bs/hal/hal_intf.c b/drivers/staging/rtl8723bs/hal/hal_intf.c
index 2caade1a8..1096f5441 100644
--- a/drivers/staging/rtl8723bs/hal/hal_intf.c
+++ b/drivers/staging/rtl8723bs/hal/hal_intf.c
@@ -89,7 +89,8 @@ u8 rtw_hal_get_def_var(struct adapter *padapter, enum hal_def_variable eVariable
 	return GetHalDefVar8723BSDIO(padapter, eVariable, pValue);
 }
 
-void rtw_hal_set_odm_var(struct adapter *padapter, enum hal_odm_variable eVariable, void *pValue1, bool bSet)
+void rtw_hal_set_odm_var(struct adapter *padapter,
+			 enum hal_odm_variable eVariable, void *pValue1, bool bSet)
 {
 	SetHalODMVar(padapter, eVariable, pValue1, bSet);
 }
@@ -216,7 +217,8 @@ void rtw_hal_dm_watchdog(struct adapter *padapter)
 void rtw_hal_dm_watchdog_in_lps(struct adapter *padapter)
 {
 	if (adapter_to_pwrctl(padapter)->fw_current_in_ps_mode)
-		rtl8723b_HalDmWatchDog_in_LPS(padapter); /* this function caller is in interrupt context */
+		/* this function caller is in interrupt context */
+		rtl8723b_HalDmWatchDog_in_LPS(padapter);
 }
 
 void beacon_timing_control(struct adapter *padapter)
-- 
2.55.0.windows.3


                 reply	other threads:[~2026-09-09 17:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260909174152.16934-1-t+linux@prudhomme.li \
    --to=t+linux@prudhomme.li \
    --cc=gregkh@linuxfoundation.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