From: Dan Carpenter <dan.carpenter@linaro.org>
To: Rohan Tripathi <trohan2000@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: clean up style in rtw_ap.c
Date: Mon, 6 Oct 2025 10:29:20 +0300 [thread overview]
Message-ID: <aONv0JIZNA2GPzKG@stanley.mountain> (raw)
In-Reply-To: <20251005155920.381334-2-trohan2000@gmail.com>
On Sun, Oct 05, 2025 at 11:59:17AM -0400, Rohan Tripathi wrote:
> This patch fixes several coding style issues reported by checkpatch.pl
> in rtw_ap.c. Changes include:
> - Removed cases where lines ended with an opening parenthesis
> - Broke long comments exceeding 100 characters
> - Fixed alignment in multi-line function calls
>
> These are coding style cleanups only. No functional changes.
>
> Signed-off-by: Rohan Tripathi <trohan2000@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_ap.c | 270 +++++++++++-------------
> 1 file changed, 123 insertions(+), 147 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_ap.c b/drivers/staging/rtl8723bs/core/rtw_ap.c
> index 0908f2234f67..9aa225bcf9d6 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_ap.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_ap.c
> @@ -391,7 +391,9 @@ void update_bmc_sta(struct adapter *padapter)
>
> memset((void *)&psta->sta_stats, 0, sizeof(struct stainfo_stats));
>
> - /* psta->dot118021XPrivacy = _NO_PRIVACY_;//!!! remove it, because it has been set before this. */
> + /* psta->dot118021XPrivacy = _NO_PRIVACY_;
> + * remove it, because it has been set before this.
> + */
Just delete dead code.
>
> /* prepare for add_RATid */
> supportRateNum = rtw_get_rateset_len((u8 *)&pcur_network->supported_rates);
> @@ -436,7 +438,6 @@ void update_bmc_sta(struct adapter *padapter)
> spin_lock_bh(&psta->lock);
> psta->state = _FW_LINKED;
> spin_unlock_bh(&psta->lock);
> -
> }
This is fine, but it's unrelated to the rest of the patch so it needs to
be done as a separate patch.
> }
>
> @@ -480,14 +481,13 @@ void update_sta_info_apmode(struct adapter *padapter, struct sta_info *psta)
> /* check if sta supports rx ampdu */
> phtpriv_sta->ampdu_enable = phtpriv_ap->ampdu_enable;
>
> - phtpriv_sta->rx_ampdu_min_spacing = (
> - phtpriv_sta->ht_cap.ampdu_params_info & IEEE80211_HT_CAP_AMPDU_DENSITY
> + phtpriv_sta->rx_ampdu_min_spacing = (phtpriv_sta->ht_cap.ampdu_params_info &
> + IEEE80211_HT_CAP_AMPDU_DENSITY
> ) >> 2;
>
> /* bwmode */
> - if ((
> - phtpriv_sta->ht_cap.cap_info & phtpriv_ap->ht_cap.cap_info
> - ) & cpu_to_le16(IEEE80211_HT_CAP_SUP_WIDTH))
> + if ((phtpriv_sta->ht_cap.cap_info & phtpriv_ap->ht_cap.cap_info) &
> + cpu_to_le16(IEEE80211_HT_CAP_SUP_WIDTH))
This isn't aligned correctly. Use a combination of tabs and spaces to
make it exact.
Same for all the rest etc.
regards,
dan carpenter
next prev parent reply other threads:[~2025-10-06 7:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-05 15:59 [PATCH 1/4] staging: rtl8723bs: clean up lines ending with '(' in rtw_ap.c Rohan Tripathi
2025-10-05 15:59 ` [PATCH] staging: rtl8723bs: clean up style " Rohan Tripathi
2025-10-06 7:29 ` Dan Carpenter [this message]
2025-10-05 15:59 ` [PATCH 2/4] staging: rtl8723bs: split long comments " Rohan Tripathi
2025-10-06 7:30 ` Dan Carpenter
2025-10-05 15:59 ` [PATCH 3/4] staging: rtl8723bs: remove unnecessary blank lines " Rohan Tripathi
2025-10-06 7:30 ` Dan Carpenter
2025-10-05 15:59 ` [PATCH 4/4] staging: rtl8723bs: fix operator spacing " Rohan Tripathi
2025-10-06 7:26 ` [PATCH 1/4] staging: rtl8723bs: clean up lines ending with '(' " Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2025-10-05 13:55 [PATCH] staging: rtl8723bs: clean up style " Rohan Tripathi
2025-10-05 14:23 ` Greg KH
2025-10-05 14:23 ` Greg KH
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=aONv0JIZNA2GPzKG@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=trohan2000@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.