From: Ria Thomas <ria.thomas@morsemicro.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
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 16:09:29 +0530 [thread overview]
Message-ID: <20251125103929.g7biphcys3d52dhi@1207> (raw)
In-Reply-To: <41f2d55eb0921a95db6a3445800df67dfe99e7ee.camel@sipsolutions.net>
On Tue, Nov 25, 2025 at 10:30:37AM +0100, Johannes Berg wrote:
>
> I did apply this now, but I do wonder if we're better off just removing
> unused values? We don't (even pretend to) maintain a full definition of
> everything 802.11 in the kernel, and don't need to either?
>
> johannes
Thanks for applying.
For context, I’m not using these status codes directly today. The change was
mainly to unblock the enum space for upcoming NDP work. This adjustment was necessary
to remove a dependency blocker in my series.
I’m fine with removing unused values altogether. If you prefer, I can follow up with a
cleanup patch that drops unused codes and adds a brief comment noting the list isn’t
exhaustive and new codes should be added on demand.
Ria
prev parent reply other threads:[~2025-11-25 10: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
2025-11-25 9:30 ` Johannes Berg
2025-11-25 10:39 ` Ria Thomas [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=20251125103929.g7biphcys3d52dhi@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