From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Timo Joannin <timo.joannin@gmail.com>
Cc: "Jennifer Guo" <guojy.bj@gmail.com>,
"Michael Straube" <straube.linux@gmail.com>,
"Michael Steinmötzger" <m.steinmoetzger@gmail.com>,
"Dan Carpenter" <error27@gmail.com>,
"Atharv Margur" <atharvmargur@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: rename phy_status_rpt_8192cd_t to rtl8723bs_phy_status_rpt.
Date: Thu, 1 Oct 2026 14:26:58 +0200 [thread overview]
Message-ID: <2026100112-impotent-undiluted-d9de@gregkh> (raw)
In-Reply-To: <20261001121700.143861-1-timo.joannin@gmail.com>
On Thu, Oct 01, 2026 at 02:17:00PM +0200, Timo Joannin wrote:
> The struct identifier references the 8192CD chip while being in a
> rtl8723bs codebase. Additionally, the identifier uses the _t suffix,
> while being generally reserved for typedef identifiers.
>
> Rename the struct to rtl8723bs_phy_status_rpt
> across the rtl8723bs driver to accurately
> reflect the codebase and clean up the naming.
>
> Signed-off-by: Timo Joannin <timo.joannin@gmail.com>
> ---
> drivers/staging/rtl8723bs/hal/odm_HWConfig.c | 3 ++-
> drivers/staging/rtl8723bs/hal/odm_HWConfig.h | 2 +-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/hal/odm_HWConfig.c b/drivers/staging/rtl8723bs/hal/odm_HWConfig.c
> index 34b0369a7936..bf2479c01873 100644
> --- a/drivers/staging/rtl8723bs/hal/odm_HWConfig.c
> +++ b/drivers/staging/rtl8723bs/hal/odm_HWConfig.c
> @@ -105,7 +105,8 @@ static void odm_rx_phy_status_parsing(struct dm_odm_t *dm_odm,
> bool is_cck_rate = false;
> u8 rf_rx_num = 0;
> u8 lna_idx, vga_idx;
> - struct phy_status_rpt_8192cd_t *phy_sta_rpt = (struct phy_status_rpt_8192cd_t *)phy_status;
> + struct rtl8723bs_phy_status_rpt *phy_sta_rpt =
> + (struct rtl8723bs_phy_status_rpt *)phy_status;
Why is this pointer being cast from a structure type, to a u8 *, and now
back to the real structure again? That's a mess, please propagate the
real structure type all the way through the call chain so that there is
no more casts needed.
thanks,
greg k-h
prev parent reply other threads:[~2026-10-01 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 12:17 [PATCH] staging: rtl8723bs: rename phy_status_rpt_8192cd_t to rtl8723bs_phy_status_rpt Timo Joannin
2026-10-01 12:26 ` Greg Kroah-Hartman [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=2026100112-impotent-undiluted-d9de@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=atharvmargur@gmail.com \
--cc=error27@gmail.com \
--cc=guojy.bj@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=m.steinmoetzger@gmail.com \
--cc=straube.linux@gmail.com \
--cc=timo.joannin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.