From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thomas Prud'homme <t+linux@prudhomme.li>
Cc: linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: rtl8723bs: fix lines over 100 characters in hal_intf.c
Date: Thu, 1 Oct 2026 07:41:13 +0200 [thread overview]
Message-ID: <2026100148-elixir-depose-a7df@gregkh> (raw)
In-Reply-To: <20260909174152.16934-1-t+linux@prudhomme.li>
On Wed, Sep 09, 2026 at 07:41:52PM +0200, Thomas Prud'homme wrote:
> 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);
Doesn't this break a different checkpatch issue?
Be careful of multi-line statements like this...
thanks,
greg k-h
next prev parent reply other threads:[~2026-10-01 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 17:41 [PATCH] staging: rtl8723bs: fix lines over 100 characters in hal_intf.c Thomas Prud'homme
2026-10-01 5:41 ` Greg Kroah-Hartman [this message]
2026-10-01 11:48 ` Dan Carpenter
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=2026100148-elixir-depose-a7df@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
--cc=t+linux@prudhomme.li \
/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