From: Greg KH <gregkh@linuxfoundation.org>
To: Xiyuan Guo <tommyguo039@gmail.com>
Cc: error27@gmail.com, b9788213@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: rtl8723bs: fix CamelCase warning for READ_MACREG
Date: Tue, 31 Mar 2026 10:41:14 +0200 [thread overview]
Message-ID: <2026033156-resale-pug-5aae@gregkh> (raw)
In-Reply-To: <20260331043954.5400-1-tommyguo039@gmail.com>
On Tue, Mar 31, 2026 at 12:39:54AM -0400, Xiyuan Guo wrote:
> Rename the _Read_MACREG macro to READ_MACREG to resolve the checkpatch.pl
> "Avoid CamelCase" warning. This aligns the macro naming with the kernel
> coding style guidelines.
>
> Signed-off-by: Xiyuan Guo <tommyguo039@gmail.com>
> ---
> Changes in v3:
> - Dropped unrelated whitespace modifications caught by maintainers.
> - Rebased onto staging-next.
>
> drivers/staging/rtl8723bs/core/rtw_cmd.c | 2 +-
> drivers/staging/rtl8723bs/include/rtw_cmd.h | 2 +-
> drivers/staging/rtl8723bs/include/rtw_mlme_ext.h | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_cmd.c b/drivers/staging/rtl8723bs/core/rtw_cmd.c
> index c1185c25ed36..eb902c810ac8 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_cmd.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_cmd.c
> @@ -11,7 +11,7 @@
> #include <linux/delay.h>
>
> static struct _cmd_callback rtw_cmd_callback[] = {
> - {GEN_CMD_CODE(_Read_MACREG), NULL}, /*0*/
> + {GEN_CMD_CODE(READ_MACREG), NULL}, /*0*/
Ok, but now what does the result look like? You are creating a function
name called cmdREAD_MACREG(), is that intended?
That's why those leading '_' characters are there.
How about unwinding this mess of function pointers and #defines
entirely? It's not needed and is just yet-another layer of indirection
in this driver that needs to be removed.
thanks,
greg k-h
prev parent reply other threads:[~2026-03-31 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 4:39 [PATCH v3] staging: rtl8723bs: fix CamelCase warning for READ_MACREG Xiyuan Guo
2026-03-31 8:41 ` Greg KH [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=2026033156-resale-pug-5aae@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=b9788213@gmail.com \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=tommyguo039@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