From: Greg KH <gregkh@linuxfoundation.org>
To: Artur Ugnivenko <artur.ugnivenko@gmx.de>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
ahmet@sezginduran.net, error27@gmail.com
Subject: Re: [PATCH v5 4/4] staging: rtl8723bs: fix lines ending in parentheses in hal/sdio_halinit.c
Date: Fri, 22 May 2026 07:09:03 +0200 [thread overview]
Message-ID: <2026052200-leotard-overprice-bb1f@gregkh> (raw)
In-Reply-To: <20260521125604.4688-1-artur.ugnivenko@gmx.de>
On Thu, May 21, 2026 at 02:56:04PM +0200, Artur Ugnivenko wrote:
> Fix checkpatch warnings on lines that end in patentheses in
> hal/sdio_halinit.c.
>
> Signed-off-by: Artur Ugnivenko <artur.ugnivenko@gmx.de>
> ---
> drivers/staging/rtl8723bs/hal/sdio_halinit.c | 49 ++++++++++----------
> 1 file changed, 25 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/hal/sdio_halinit.c b/drivers/staging/rtl8723bs/hal/sdio_halinit.c
> index e6570fa2e8fd..494fb74ad44f 100644
> --- a/drivers/staging/rtl8723bs/hal/sdio_halinit.c
> +++ b/drivers/staging/rtl8723bs/hal/sdio_halinit.c
> @@ -74,7 +74,7 @@ u8 _InitPowerOn_8723BS(struct adapter *padapter)
> rtw_write8(padapter, REG_CR, 0x00);
> /* Enable MAC DMA/WMAC/SCHEDULE/SEC block */
> value16 = rtw_read16(padapter, REG_CR);
> - value16 |= (
> + value16 |=
> HCI_TXDMA_EN |
> HCI_RXDMA_EN |
> TXDMA_EN |
> @@ -82,8 +82,7 @@ u8 _InitPowerOn_8723BS(struct adapter *padapter)
> PROTOCOL_EN |
> SCHEDULE_EN |
> ENSEC |
> - CALTMR_EN
> - );
> + CALTMR_EN;
The original () is ok to keep.
> rtw_write16(padapter, REG_CR, value16);
>
> hal_btcoex_PowerOnSetting(padapter);
> @@ -188,15 +187,13 @@ static void _InitTxBufferBoundary(struct adapter *padapter)
> rtw_write8(padapter, REG_TDECTRL + 1, txpktbuf_bndy);
> }
>
> -static void _InitNormalChipRegPriority(
> - struct adapter *Adapter,
> - u16 beQ,
> - u16 bkQ,
> - u16 viQ,
> - u16 voQ,
> - u16 mgtQ,
> - u16 hiQ
> -)
> +static void _InitNormalChipRegPriority(struct adapter *Adapter,
> + u16 beQ,
> + u16 bkQ,
> + u16 viQ,
> + u16 voQ,
> + u16 mgtQ,
> + u16 hiQ)
You can do better than this :)
try making it multiple variables per line.
> {
> u16 value16 = (rtw_read16(Adapter, REG_TRXDMA_CTRL) & 0x7);
>
> @@ -231,9 +228,13 @@ static void _InitNormalChipOneOutEpPriority(struct adapter *Adapter)
> break;
> }
>
> - _InitNormalChipRegPriority(
> - Adapter, value, value, value, value, value, value
> - );
> + _InitNormalChipRegPriority(Adapter,
> + value,
> + value,
> + value,
> + value,
> + value,
> + value);
That's crazy, perhaps the function should be changed?
thanks,
greg k-h
prev parent reply other threads:[~2026-05-22 5:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 11:23 [PATCH v5 0/4] staging: rtl8723bs: fix several style issues in hal/sdio_halinit.c Artur Ugnivenko
2026-05-21 11:23 ` [PATCH v5 1/4] staging: rtl8723bs: shorten long lines " Artur Ugnivenko
2026-05-21 11:23 ` [PATCH v5 2/4] staging: rtl8723bs: fix inconsistent braces " Artur Ugnivenko
2026-05-21 11:23 ` [PATCH v5 3/4] staging: rtl8723bs: remove excessive whitespace " Artur Ugnivenko
2026-05-21 11:28 ` Ahmet Sezgin Duran
2026-05-21 12:56 ` [PATCH v5 4/4] staging: rtl8723bs: fix lines ending in parentheses " Artur Ugnivenko
2026-05-22 5:09 ` Greg KH [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=2026052200-leotard-overprice-bb1f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ahmet@sezginduran.net \
--cc=artur.ugnivenko@gmx.de \
--cc=error27@gmail.com \
--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