From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Azamat Rakhim" <azamatrakhim8@gmail.com>, <gregkh@linuxfoundation.org>
Cc: <karanja99erick@gmail.com>, <linux-staging@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723bs: clean up checkpatch warnings in rtw_btcoex.c
Date: Sat, 07 Feb 2026 16:31:18 -0600 [thread overview]
Message-ID: <DG933PFQ8WC8.T2CFFOKHSDDX@gmail.com> (raw)
In-Reply-To: <20260207210124.10094-1-azamatrakhim8@gmail.com>
On Sat Feb 7, 2026 at 3:01 PM CST, Azamat Rakhim wrote:
> Remove unnecessary comparison to true and extra blank lines
> to address checkpatch warnings.
>
> Signed-off-by: Azamat Rakhim <azamatrakhim8@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_btcoex.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_btcoex.c b/drivers/staging/rtl8723bs/core/rtw_btcoex.c
> index f4b19ef7b341..8c17ac994bbc 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_btcoex.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_btcoex.c
> @@ -11,7 +11,7 @@
> void rtw_btcoex_MediaStatusNotify(struct adapter *padapter, u8 media_status)
> {
> if ((media_status == RT_MEDIA_CONNECT)
> - && (check_fwstate(&padapter->mlmepriv, WIFI_AP_STATE) == true)) {
> + && (check_fwstate(&padapter->mlmepriv, WIFI_AP_STATE))) {
> rtw_hal_set_hwreg(padapter, HW_VAR_DL_RSVD_PAGE, NULL);
> }
You fixed one checkpatch.pl error on this line, but left another one.
Logical operators need to go at the end of the previous line
not the beginning of it. So that'd be "if ((media_status ==
RT_MEDIA_CONNECT) &&".
>
> @@ -54,7 +54,6 @@ void rtw_btcoex_LPS_Enter(struct adapter *padapter)
> struct pwrctrl_priv *pwrpriv;
> u8 lps_val;
>
> -
> pwrpriv = adapter_to_pwrctl(padapter);
>
> pwrpriv->bpower_saving = true;
> @@ -66,7 +65,6 @@ void rtw_btcoex_LPS_Leave(struct adapter *padapter)
> {
> struct pwrctrl_priv *pwrpriv;
>
> -
> pwrpriv = adapter_to_pwrctl(padapter);
>
> if (pwrpriv->pwr_mode != PS_MODE_ACTIVE) {
These whitespace fixes should be their own patch. Please keep one
logical change per patch.
Also, your subject line should say what you fixed not the tool you used to
find it. Next time before sending patches off run "$
./scripts/checkpatch.pl --strict <patch>" to find problems like this.
Thanks,
ET
prev parent reply other threads:[~2026-02-07 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 21:01 [PATCH] staging: rtl8723bs: clean up checkpatch warnings in rtw_btcoex.c Azamat Rakhim
2026-02-07 22:31 ` Ethan Tidmore [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=DG933PFQ8WC8.T2CFFOKHSDDX@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=azamatrakhim8@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=karanja99erick@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