Linux kernel staging patches
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thomas Prud'homme <t+linux@prudhomme.li>, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: rtl8723bs: fix lines over 100 characters in hal_intf.c
Date: Thu, 1 Oct 2026 14:48:42 +0300	[thread overview]
Message-ID: <ar5ImtTs5L-p9rwD@stanley.mountain> (raw)
In-Reply-To: <2026100148-elixir-depose-a7df@gregkh>

On Thu, Oct 01, 2026 at 07:41:13AM +0200, Greg Kroah-Hartman wrote:
> 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?
> 

No, it doesn't.  But, of course, yes, multi-line if statements should
get curly braces.  It's an unwritten rule.

Also I feel like loop macros should get curly braces as well but that
might just be me...

regards,
dan carpenter


      reply	other threads:[~2026-10-01 11:48 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
2026-10-01 11:48   ` Dan Carpenter [this message]

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=ar5ImtTs5L-p9rwD@stanley.mountain \
    --to=error27@gmail.com \
    --cc=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