From: Johannes Berg <johannes@sipsolutions.net>
To: Pablo Martin-Gomez <pmartin-gomez@freebox.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/3] EML Capabilities compliance changes
Date: Tue, 07 Apr 2026 11:00:18 +0200 [thread overview]
Message-ID: <e492c443eee0918690a842d9d2eaaf23c2126473.camel@sipsolutions.net> (raw)
In-Reply-To: <20260327201135.905852-1-pmartin-gomez@freebox.fr> (sfid-20260327_211151_662542_5A83B71C)
On Fri, 2026-03-27 at 21:11 +0100, Pablo Martin-Gomez wrote:
> There is some discrepencies between our codebase and the final version
> of 802.11be-2024 regarding the EML Capabilities field. Given that no
> driver supports EMLMR or tries to use 128TUs transition timeout, those
> changes should not have any real impact.
Heh, funny, I noticed this a while ago too - it must've been in an
earlier draft. And UHR has the same - but *does* (for now :) ) define
128 TU (which is why I noticed it.)
johannes
prev parent reply other threads:[~2026-04-07 9:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 20:11 [PATCH 0/3] EML Capabilities compliance changes Pablo Martin-Gomez
2026-03-27 20:11 ` [PATCH 1/3] wifi: Transition Timeout of 128TUs is not defined Pablo Martin-Gomez
2026-03-27 20:11 ` [PATCH 2/3] wifi: EMLMR Delay subfield has been removed Pablo Martin-Gomez
2026-03-27 20:11 ` [PATCH 3/3] wifi: Transition/Padding delay subfields are for both EMLSR and EMLMR Pablo Martin-Gomez
2026-04-07 14:00 ` Johannes Berg
2026-04-07 15:47 ` Pablo MARTIN-GOMEZ
2026-04-08 12:07 ` Johannes Berg
2026-04-09 9:04 ` Pablo MARTIN-GOMEZ
2026-04-09 13:14 ` Johannes Berg
2026-04-07 9:00 ` Johannes Berg [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=e492c443eee0918690a842d9d2eaaf23c2126473.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pmartin-gomez@freebox.fr \
/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