From: Johannes Berg <johannes@sipsolutions.net>
To: Karthikeyan Kathirvel <karthikeyan.kathirvel@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH RFC wireless-next 00/13] wifi: ieee80211/cfg80211: Add UHR (802.11bn) Capability and Operation support
Date: Tue, 16 Dec 2025 10:04:24 +0100 [thread overview]
Message-ID: <07cab823d7695b20aa7ddb1b3698e5eb88ff2c9c.camel@sipsolutions.net> (raw)
In-Reply-To: <20251216062656.1738022-1-karthikeyan.kathirvel@oss.qualcomm.com>
On Tue, 2025-12-16 at 11:56 +0530, Karthikeyan Kathirvel wrote:
> This series covers support for UHR capability and operation (11bn)
> advertisement in AP and STA mode. The objective here is to give an
> idea of basic changes needed for UHR in cfg80211/nl80211/mac80211.
Huh. I never posted my version, sorry about that! I'll see if I can do
that soon so we can compare notes, but I'll also go over yours quickly.
johannes
next prev parent reply other threads:[~2025-12-16 9:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 6:26 [PATCH RFC wireless-next 00/13] wifi: ieee80211/cfg80211: Add UHR (802.11bn) Capability and Operation support Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 01/13] wifi: nl80211: reduce multiple deference of link_sta_params Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 02/13] wifi: ieee80211: Add UHR (802.11bn) definitions Karthikeyan Kathirvel
2025-12-16 9:08 ` Johannes Berg
2025-12-17 12:54 ` Karthikeyan Kathirvel
2025-12-17 12:55 ` Johannes Berg
2025-12-17 12:56 ` Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 03/13] wifi: cfg80211: Add data structures to capture UHR capabilities Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 04/13] wifi: cfg80211: add a helper function to return the UHR interface capabilities Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 05/13] wifi: cfg80211: Support configuration of station UHR capabilities Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 06/13] wifi: nl80211: retrieve UHR related elements in AP mode Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 07/13] wifi: nl80211/reg: add no-UHR regulatory flag Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 08/13] wifi: mac80211: Support parsing UHR elements Karthikeyan Kathirvel
2025-12-16 9:10 ` Johannes Berg
2025-12-16 6:26 ` [PATCH RFC wireless-next 09/13] wifi: mac80211: Add UHR capabilities to association/probe request for STA mode Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 10/13] wifi: mac80211: Handle station association response with UHR Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 11/13] wifi: mac80211: set UHR support flag in AP mode Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 12/13] wifi: cfg80211: support disabling UHR mode Karthikeyan Kathirvel
2025-12-16 6:26 ` [PATCH RFC wireless-next 13/13] wifi: mac80211_hwsim: Add UHR capabilities in driver Karthikeyan Kathirvel
2025-12-16 9:04 ` Johannes Berg [this message]
2025-12-16 9:12 ` [PATCH RFC wireless-next 00/13] wifi: ieee80211/cfg80211: Add UHR (802.11bn) Capability and Operation support Johannes Berg
2025-12-17 10:05 ` Karthikeyan Kathirvel
2025-12-22 11:59 ` Karthikeyan Kathirvel
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=07cab823d7695b20aa7ddb1b3698e5eb88ff2c9c.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=karthikeyan.kathirvel@oss.qualcomm.com \
--cc=linux-wireless@vger.kernel.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