From: Johannes Berg <johannes@sipsolutions.net>
To: radiotap@netbsd.org
Subject: [PATCH] EHT: list a reserved bit
Date: Wed, 8 Oct 2025 17:05:13 +0200 [thread overview]
Message-ID: <20251008150513.25206-1-johannes@sipsolutions.net> (raw)
This bit was previously not listed at all, correctly list
it as reserved.
---
fields/EHT.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fields/EHT.md b/fields/EHT.md
index 01cbf159d7a9..e24a69c7c6f0 100644
--- a/fields/EHT.md
+++ b/fields/EHT.md
@@ -86,7 +86,7 @@ Some values here could also appear for non-OFDMA PPDUs.
| **`0x00001fe0`** | RU/MRU Index (see IEEE 802.11be Draft 1.3 section 36.3.2 "Subcarrier and resource allocation") |
| **`0x003fe000`** | RU Allocation 1 |
| **`0x00400000`** | RU Allocation 1 known |
-| **`0x3f000000`** | (reserved) |
+| **`0x3f800000`** | (reserved) |
| **`0xc0000000`** | Primary 80 MHz Channel Position (0: lowest, 3: highest in frequency)|
Note: The RU/MRU Size and RU/MRU Index are calculated fields, ideally the
--
2.51.0
reply other threads:[~2025-10-08 15:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251008150513.25206-1-johannes@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=radiotap@netbsd.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).