From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ethan Tidmore <ethantidmore06@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Michael Straube <straube.linux@gmail.com>,
Hans de Goede <hansg@kernel.org>,
Akiyoshi Kurita <weibu@redadmin.org>,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH v1] staging: rtl8723bs: rename members of struct registry_priv
Date: Mon, 26 Jan 2026 15:32:31 +0100 [thread overview]
Message-ID: <2026012647-overheat-elm-aecc@gregkh> (raw)
In-Reply-To: <20260126141543.2527-1-ethantidmore06@gmail.com>
On Mon, Jan 26, 2026 at 08:15:43AM -0600, Ethan Tidmore wrote:
> Rename CamelCase members of struct registry_priv to snake_case to
> comply with the Linux kernel coding style.
Close, but:
> + u8 b_en_rfe;
What does the "b_" here mean? The original variable name had it, but
that was because it was attempting to do a "hungarian notation" type of
name, which is not the correct way to name Linux kernel variables,
sorry.
Also:
> --- a/drivers/staging/rtl8723bs/include/hal_com_phycfg.h
> +++ b/drivers/staging/rtl8723bs/include/hal_com_phycfg.h
> @@ -90,7 +90,7 @@ void PHY_TxPowerByRateConfiguration(struct adapter *padapter);
> u8 PHY_GetTxPowerIndexBase(struct adapter *padapter, u8 RFPath, u8 Rate,
> enum channel_width BandWidth, u8 Channel);
>
> -s8 phy_get_tx_pwr_lmt(struct adapter *adapter, u32 RegPwrTblSel,
> +s8 phy_get_tx_pwr_lmt(struct adapter *adapter, u32 reg_pwr_tbl_sel,
That was not a change needed do to the structure name changes. Please
only do one logical change per patch. Maybe one per variable name
change to make it more obvious and easy to review?
thanks,
greg k-h
next prev parent reply other threads:[~2026-01-26 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 14:15 [PATCH v1] staging: rtl8723bs: rename members of struct registry_priv Ethan Tidmore
2026-01-26 14:32 ` Greg Kroah-Hartman [this message]
2026-01-27 6:26 ` Dan Carpenter
2026-01-27 7:43 ` Ethan Tidmore
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=2026012647-overheat-elm-aecc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@linaro.org \
--cc=ethantidmore06@gmail.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=straube.linux@gmail.com \
--cc=weibu@redadmin.org \
/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