From: Ria Thomas <ria.thomas@morsemicro.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
lachlan.hodges@morsemicro.com, pradeep.reddy@morsemicro.com,
simon@morsemicro.com
Subject: Re: [PATCH v2] wifi: mac80211: correct FILS status codes
Date: Tue, 25 Nov 2025 09:09:15 +0530 [thread overview]
Message-ID: <20251125033915.3m2uczkde2nqcoya@1207> (raw)
In-Reply-To: <29ebeb55-1528-42b0-a692-11f20097fca8@oss.qualcomm.com>
On Mon, Nov 24, 2025 at 09:52:31AM -0800, Jeff Johnson wrote:
> On 11/24/2025 4:56 AM, Ria Thomas wrote:
> > The FILS status codes are set to 108/109, but the IEEE 802.11-2020
>
> Note that the current version is IEEE Std 802.11-2024, and it would be useful
> to directly reference Table 9-80.
Thanks, I've noted that the current revision is 802.11-2024.I cited
802.11-2020 because it’s the first revision that defines these status
codes. I can switch to 802.11-2024 if that’s preferred.
>
> This issue was pointed out by IEEE in "Errata to IEEE Std 802.11ai-2016." In
> addition to this issue, that errata also calls out renumbering the "Category
> values" in what was then Table 9-47, now Table 9-81, for FILS from 22 to 26.
> But the current enum ieee80211_category does not have an entry for FILS, so
> that part of the errata does not need to be applied
>
> But while researching this I see the current category 22 enum is incorrect:
> WLAN_CATEGORY_S1G = 22,
>
> since IEEE Std 802.11-2024, Table 9-81 has:
> 22 Unprotected S1G
> 23 S1G
>
> So that might also need to be addressed by someone.
>
Sure, will review the changes and submit the patch separately as S1G related change.
next prev parent reply other threads:[~2025-11-25 3:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 6:11 [PATCH wireless] wifi: mac80211: correct FILS status codes Ria Thomas
2025-11-24 11:58 ` Johannes Berg
2025-11-24 12:44 ` Pablo MARTIN-GOMEZ
2025-11-25 3:25 ` Ria Thomas
2025-11-24 12:56 ` [PATCH v2] " Ria Thomas
2025-11-24 17:52 ` Jeff Johnson
2025-11-25 3:39 ` Ria Thomas [this message]
2025-11-25 9:30 ` Johannes Berg
2025-11-25 10:39 ` Ria Thomas
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=20251125033915.3m2uczkde2nqcoya@1207 \
--to=ria.thomas@morsemicro.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=lachlan.hodges@morsemicro.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pradeep.reddy@morsemicro.com \
--cc=simon@morsemicro.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