Linux kernel staging patches
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Yao-Wen Chang <changyaowen19980629@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/11] staging: rtl8723bs: Reformat code to respect 100-column line limit
Date: Mon, 11 Aug 2025 10:30:11 +0300	[thread overview]
Message-ID: <aJmcA7SlCjXXPsOl@stanley.mountain> (raw)
In-Reply-To: <20250811062132.102525-2-changyaowen19980629@gmail.com>

On Mon, Aug 11, 2025 at 02:21:25PM +0800, Yao-Wen Chang wrote:
> This commit breaks several long lines of code to ensure they do not exceed
> the 100-character limit.
> 
> Signed-off-by: Yao-Wen Chang <changyaowen19980629@gmail.com>
> ---
>  drivers/staging/rtl8723bs/core/rtw_ap.c  |  12 ++-
>  drivers/staging/rtl8723bs/core/rtw_cmd.c | 106 ++++++++++++++++-------
>  2 files changed, 83 insertions(+), 35 deletions(-)
> 
> diff --git a/drivers/staging/rtl8723bs/core/rtw_ap.c b/drivers/staging/rtl8723bs/core/rtw_ap.c
> index 47c63177b2a6..2e59a26e6318 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.
> +		 */

Delete commented out code.  Also what the heck is up with "* //!!! remove it, ".

>  
>  		/* prepare for add_RATid */
>  		supportRateNum = rtw_get_rateset_len((u8 *)&pcur_network->supported_rates);
> @@ -841,7 +843,9 @@ int rtw_check_beacon_data(struct adapter *padapter, u8 *pbuf,  int len)
>  	memcpy(pbss_network->mac_address, myid(&padapter->eeprompriv), ETH_ALEN);
>  
>  	/* beacon interval */
> -	p = rtw_get_beacon_interval_from_ie(ie);/* ie + 8;	8: TimeStamp, 2: Beacon Interval 2:Capability */
> +	p = rtw_get_beacon_interval_from_ie(ie); /* ie + 8; 8:
> +						  *TimeStamp, 2: Beacon Interval 2:Capability
> +						  */

This is whack.  Just go through the rest of the patchset and really
think about things a little bit more carefully.  We could obviously
have fixed all the checkpatch patches automatically and there is a
checkpatch option to do that, but we want people to do it manually
and really review things in context.

regards,
dan carpenter


  reply	other threads:[~2025-08-11  7:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11  6:21 [PATCH 01/11] staging: rtl8723bs: Rename camelCase variables to snake_case Yao-Wen Chang
2025-08-11  6:21 ` [PATCH 02/11] staging: rtl8723bs: Reformat code to respect 100-column line limit Yao-Wen Chang
2025-08-11  7:30   ` Dan Carpenter [this message]
2025-08-11  6:21 ` [PATCH 03/11] staging: rtl8723bs: Remove empty line Yao-Wen Chang
2025-08-11  6:21 ` [PATCH 04/11] staging: rtl8723bs: Fix the line end with ( issue Yao-Wen Chang
2025-08-11  6:21 ` [PATCH 05/11] staging: rtl8723bs: Rmove unnecessary parentheses around the statement Yao-Wen Chang
2025-08-11  6:21 ` [PATCH 06/11] staging: rtl8723bs: Remove redundant comparison to true and false Yao-Wen Chang
2025-08-11  6:21 ` [PATCH 07/11] staging: rtl8723bs: Add spaces around binary operators Yao-Wen Chang
2025-08-11  6:21 ` [PATCH 08/11] staging: rtl8723bs: Enforce alignment match open parenthesis Yao-Wen Chang
2025-08-11  6:21 ` [PATCH 09/11] staging: rtl8723bs: Rename camelCaseVar to snake_case_var Yao-Wen Chang
2025-08-11  7:24 ` [PATCH 01/11] staging: rtl8723bs: Rename camelCase variables to snake_case Dan Carpenter

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=aJmcA7SlCjXXPsOl@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=changyaowen19980629@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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