public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 1/4] staging: rtl8723bs: clean up lines ending with '(' in rtw_ap.c
Date: Mon, 6 Oct 2025 10:26:50 +0300	[thread overview]
Message-ID: <aONvOsbVxGYKZnvD@stanley.mountain> (raw)
In-Reply-To: <20251005155920.381334-1-trohan2000@gmail.com>

On Sun, Oct 05, 2025 at 11:59:16AM -0400, Rohan Tripathi wrote:
> This patch fixes coding style issues where lines ended with an opening
> parenthesis. These expressions were reformatted so that opening
> parentheses remain on the same line as the statement, with proper
> alignment of continued arguments.
> 
> This is a coding style cleanup only. No functional changes.
> 
> Signed-off-by: Rohan Tripathi <trohan2000@gmail.com>
> ---

This needs to be marked as a v2:
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/

>  drivers/staging/rtl8723bs/core/rtw_ap.c | 250 +++++++++++-------------
>  1 file changed, 109 insertions(+), 141 deletions(-)
> 
> diff --git a/drivers/staging/rtl8723bs/core/rtw_ap.c b/drivers/staging/rtl8723bs/core/rtw_ap.c
> index 0908f2234f67..93ab0015ca89 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_ap.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_ap.c
> @@ -480,14 +480,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
> -		) >> 2;
> +		phtpriv_sta->rx_ampdu_min_spacing =
> +		(phtpriv_sta->ht_cap.ampdu_params_info &
> +		 IEEE80211_HT_CAP_AMPDU_DENSITY) >> 2;

No, still not nice.  I think I would go over 80 characters.

	phtpriv_sta->rx_ampdu_min_spacing = (phtpriv_sta->ht_cap.ampdu_params_info &
					     IEEE80211_HT_CAP_AMPDU_DENSITY) >> 2;

Another option would be to do:

	phtpriv_sta->rx_ampdu_min_spacing =
			(phtpriv_sta->ht_cap.ampdu_params_info &
			 IEEE80211_HT_CAP_AMPDU_DENSITY) >> 2;

> @@ -498,15 +497,13 @@ void update_sta_info_apmode(struct adapter *padapter, struct sta_info *psta)
>  		phtpriv_sta->ch_offset = pmlmeext->cur_ch_offset;
>  
>  		/* check if sta support s Short GI 20M */
> -		if ((
> -			phtpriv_sta->ht_cap.cap_info & phtpriv_ap->ht_cap.cap_info
> -		) & cpu_to_le16(IEEE80211_HT_CAP_SGI_20))
> +		if ((phtpriv_sta->ht_cap.cap_info & phtpriv_ap->ht_cap.cap_info) &
> +		cpu_to_le16(IEEE80211_HT_CAP_SGI_20))

This needs to be done like so:

		if ((phtpriv_sta->ht_cap.cap_info & phtpriv_ap->ht_cap.cap_info) &
		    cpu_to_le16(IEEE80211_HT_CAP_SGI_20))

[tab][tab][space][space][space][space]cpu_to_le16(IEEE80211_HT_CAP_SGI_20))

You get the idea.  Same for the rest of the patchset.

regards,
dan carpenter


      parent reply	other threads:[~2025-10-06  7:26 UTC|newest]

Thread overview: 9+ 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
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 ` 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=aONvOsbVxGYKZnvD@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox