From: Greg KH <gregkh@linuxfoundation.org>
To: Haroen Tmimi <tmimiharoen@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: rtl8723bs: constify _action_public_str in rtw_ieee80211.c
Date: Sat, 7 Feb 2026 14:40:27 +0100 [thread overview]
Message-ID: <2026020752-extortion-coleslaw-9687@gregkh> (raw)
In-Reply-To: <20260205120909.161336-1-tmimiharoen@gmail.com>
On Thu, Feb 05, 2026 at 01:09:09PM +0100, Haroen Tmimi wrote:
> Make the _action_public_str array "static const char * const".
>
> This ensures the array entries are read-only, preventing accidental
> modification of the pointers.
>
> Signed-off-by: Haroen Tmimi <tmimiharoen@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_ieee80211.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_ieee80211.c b/drivers/staging/rtl8723bs/core/rtw_ieee80211.c
> index 92b12a13d27c..febc14de6bc0 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_ieee80211.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_ieee80211.c
> @@ -1139,7 +1139,7 @@ int rtw_action_frame_parse(const u8 *frame, u32 frame_len, u8 *category, u8 *act
> return true;
> }
>
> -static const char *_action_public_str[] = {
> +static const char * const _action_public_str[] = {
> "ACT_PUB_BSSCOEXIST",
> "ACT_PUB_DSE_ENABLE",
> "ACT_PUB_DSE_DEENABLE",
> --
> 2.53.0
>
>
Someone already sent this same change before you did, sorry.
Why all of the same fixes for the same driver are happening at once?
Did a class just happen that encouraged people to make these types of
changes to the driver?
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-07 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 12:09 [PATCH v2] staging: rtl8723bs: constify _action_public_str in rtw_ieee80211.c Haroen Tmimi
2026-02-05 15:53 ` Ethan Tidmore
2026-02-07 13:40 ` Greg KH [this message]
2026-02-07 14:06 ` Haroen Tmimi
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=2026020752-extortion-coleslaw-9687@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=tmimiharoen@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