From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Haroen Tmimi" <tmimiharoen@gmail.com>, <gregkh@linuxfoundation.org>
Cc: <linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix checkpatch.pl warnings in rtw_ieee80211.c.
Date: Wed, 04 Feb 2026 21:39:22 -0600 [thread overview]
Message-ID: <DG6PRXWV23JA.1KGO8FYJV4M8O@gmail.com> (raw)
In-Reply-To: <20260204184133.142511-1-tmimiharoen@gmail.com>
On Wed Feb 4, 2026 at 12:41 PM CST, Haroen Tmimi wrote:
> 1. Fix "Yoda condition" style issues by moving constants to the right
> side of the comparison (e.g., changing "_SUCCESS == val" to
> "val == _SUCCESS").
>
> 2. Change the _action_public_str array to "static const char * const"
> to ensure the array entries are read-only, preventing accidental
> modification of the pointers.
>
> Signed-off-by: Haroen Tmimi <tmimiharoen@gmail.com>
> - if (_SUCCESS == rtw_parse_wpa_ie(pbuf, wpa_ielen+2, &group_cipher, &pairwise_cipher, &is8021x)) {
> + if (rtw_parse_wpa_ie(pbuf, wpa_ielen+2, &group_cipher, &pairwise_cipher, &is8021x) == _SUCCESS) {
> pnetwork->bcn_info.pairwise_cipher = pairwise_cipher;
> pnetwork->bcn_info.group_cipher = group_cipher;
> pnetwork->bcn_info.is_8021x = is8021x;
> @@ -1019,7 +1019,7 @@ static int rtw_get_cipher_info(struct wlan_network *pnetwork)
> pbuf = rtw_get_wpa2_ie(&pnetwork->network.ies[12], &wpa_ielen, pnetwork->network.ie_length-12);
>
> if (pbuf && (wpa_ielen > 0)) {
> - if (_SUCCESS == rtw_parse_wpa2_ie(pbuf, wpa_ielen+2, &group_cipher, &pairwise_cipher, &is8021x)) {
> + if (rtw_parse_wpa2_ie(pbuf, wpa_ielen+2, &group_cipher, &pairwise_cipher, &is8021x) == _SUCCESS) {
> pnetwork->bcn_info.pairwise_cipher = pairwise_cipher;
> pnetwork->bcn_info.group_cipher = group_cipher;
> pnetwork->bcn_info.is_8021x = is8021x;
> @@ -1139,7 +1139,7 @@ int rtw_action_frame_parse(const u8 *frame, u32 frame_len, u8 *category, u8 *act
> return true;
> }
This has already been fixed in staging-next. Next time use the
staging-next branch when creating patches.
>
> -static const char *_action_public_str[] = {
> +static const char * const _action_public_str[] = {
> "ACT_PUB_BSSCOEXIST",
> "ACT_PUB_DSE_ENABLE",
> "ACT_PUB_DSE_DEENABLE",
This looks good, make it it's own separate patch however. Please have
one logical change per patch.
Also, your header should have "staging: rtl8723bs" at the beginning.
Thanks.
ET
next prev parent reply other threads:[~2026-02-05 3:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 18:41 [PATCH] Fix checkpatch.pl warnings in rtw_ieee80211.c Haroen Tmimi
2026-02-05 3:39 ` Ethan Tidmore [this message]
2026-02-05 5:46 ` Dan Carpenter
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=DG6PRXWV23JA.1KGO8FYJV4M8O@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=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