From: Greg KH <gregkh@linuxfoundation.org>
To: Donny Turizo <donnyturizo13@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: rename _Read_EEPROM to _read_eeprom
Date: Thu, 22 May 2025 06:42:45 +0200 [thread overview]
Message-ID: <2025052246-boxing-swung-31b2@gregkh> (raw)
In-Reply-To: <20250522031538.30635-1-donnyturizo13@gmail.com>
On Thu, May 22, 2025 at 03:15:38AM +0000, Donny Turizo wrote:
> From: Donny-Dev <donnyturizo13@gmail.com>
>
> Fixes a checkpath warning by renaming the function
> _Read_EEPROM to follow the kernel coding style (snake_case).
Why just this one?
>
> Signed-off-by: Donny Turizo <donnyturizo13@gmail.com>
> ---
> 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 49bcefb5e8d2..a0b85beffe5d 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_cmd.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_cmd.c
> @@ -15,7 +15,7 @@ static struct _cmd_callback rtw_cmd_callback[] = {
> {GEN_CMD_CODE(_Write_BBREG), NULL},
> {GEN_CMD_CODE(_Read_RFREG), &rtw_getbbrfreg_cmdrsp_callback},
> {GEN_CMD_CODE(_Write_RFREG), NULL}, /*5*/
> - {GEN_CMD_CODE(_Read_EEPROM), NULL},
> + {GEN_CMD_CODE(_read_eeprom), NULL},
Are you sure this is correct? Aren't these commands that come from the
hardware and show up on a datasheet somewhere? Don't rename things that
are referenced outside of the kernel in a different way if at all
possible.
thanks,
greg k-h
next prev parent reply other threads:[~2025-05-22 4:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 3:15 [PATCH] staging: rtl8723bs: rename _Read_EEPROM to _read_eeprom Donny Turizo
2025-05-22 4:42 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-22 3:50 Donny Turizo
2025-05-22 4:44 ` Greg KH
2025-05-20 22:26 Donny-Dev
2025-05-21 4:21 ` 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=2025052246-boxing-swung-31b2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=donnyturizo13@gmail.com \
--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