public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Seonbin Yoon <seonbin.yoon0@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: Fix CamelCase variable name pHT_info_ie
Date: Mon, 27 Apr 2026 12:52:38 +0300	[thread overview]
Message-ID: <ae8x5glEKN_3Pnfl@stanley.mountain> (raw)
In-Reply-To: <20260427091833.30839-1-seonbin.yoon0@gmail.com>

On Mon, Apr 27, 2026 at 06:18:33PM +0900, Seonbin Yoon wrote:
> Rename variable pHT_info_ie to p_ht_info_ie to comply with
> kernel coding style (snake_case).
> 
> Fixes the following checkpatch warning:
> CHECK: Avoid CamelCase: <pHT_info_ie>
> 
> Signed-off-by: Seonbin Yoon <seonbin.yoon0@gmail.com>
> ---
>  drivers/staging/rtl8723bs/core/rtw_ap.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/rtl8723bs/core/rtw_ap.c b/drivers/staging/rtl8723bs/core/rtw_ap.c
> index 4b4012411011..2116649bab6d 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_ap.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_ap.c
> @@ -798,7 +798,7 @@ int rtw_check_beacon_data(struct adapter *padapter, u8 *pbuf,  int len)
>  	int ret = _SUCCESS;
>  	u8 *p;
>  	u8 *ht_caps_ie = NULL;
> -	u8 *pHT_info_ie = NULL;
> +	u8 *p_ht_info_ie = NULL;

p_ stands for pointer.  Get rid of that.  Just call it "ht_info_ie".

regards,
dan carpenter


  reply	other threads:[~2026-04-27  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27  9:18 [PATCH] staging: rtl8723bs: Fix CamelCase variable name pHT_info_ie Seonbin Yoon
2026-04-27  9:52 ` Dan Carpenter [this message]
2026-04-27 11:10   ` [PATCH v2] " Seonbin Yoon

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=ae8x5glEKN_3Pnfl@stanley.mountain \
    --to=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=seonbin.yoon0@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