From: Johannes Berg <johannes@sipsolutions.net>
To: Pooventhiran G <pooventhiran.g@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH wireless-next v4 13/21] wifi: mac80211: apply SMD BSS Transition STA sub-states
Date: Tue, 10 Nov 2026 21:29:29 +0100 [thread overview]
Message-ID: <f4164ec832b8dab5da90ddccc527ddcae74a44c3.camel@sipsolutions.net> (raw)
In-Reply-To: <20261106-smd-v4-13-62e39487f51a@oss.qualcomm.com>
On Fri, 2026-11-06 at 13:28 +0530, Pooventhiran G wrote:
>
> +static int sta_apply_smd_state_flags(struct sta_info *sta,
> + u32 mask, u32 set)
> +{
> + bool smd_prep_target, smd_exec_current, smd_dl_drain;
> + u32 expected_mask = BIT(NL80211_STA_FLAG_SMD_PREP_TARGET) |
> + BIT(NL80211_STA_FLAG_SMD_EXEC_CURRENT) |
> + BIT(NL80211_STA_FLAG_SMD_DL_DRAIN);
> + u32 smd_flags;
> +
> + if (!(mask & expected_mask))
> + return 0;
Not sure I'd call that "expected", it's more like "relevant" (for this
function)?
> + smd_flags = mask & expected_mask & set;
> + if (WARN_ON(hweight32(smd_flags) > 1))
> + return -EINVAL;
WARN? Isn't that potentially reachable from userspace?
> + smd_prep_target =
> + !!(smd_flags & BIT(NL80211_STA_FLAG_SMD_PREP_TARGET));
> + smd_exec_current =
> + !!(smd_flags & BIT(NL80211_STA_FLAG_SMD_EXEC_CURRENT));
> + smd_dl_drain =
> + !!(smd_flags & BIT(NL80211_STA_FLAG_SMD_DL_DRAIN));
bool, so you don't need the !!
> +
> + if (!test_sta_flag(sta, WLAN_STA_AUTHORIZED) &&
> + (smd_exec_current || smd_dl_drain))
> + return -EINVAL;
> +
> + if (smd_prep_target) {
> + clear_sta_flag(sta, WLAN_STA_SMD_EXEC_CURRENT);
> + clear_sta_flag(sta, WLAN_STA_SMD_DL_DRAIN);
> + set_sta_flag(sta, WLAN_STA_SMD_PREP_TARGET);
might be better to set then clear?
> + /*
> + * SMD BSS Transition sub-states (IEEE P802.11bn/D2.0, Aug 2026,
> + * subclause 11.3.1).
> + * Only meaningful for SMD-capable stations (WLAN_STA_SMD set).
> + */
> + if (test_sta_flag(sta, WLAN_STA_SMD)) {
> + ret = sta_apply_smd_state_flags(sta, mask, set);
Sounds more like an LLM invention than a useful comment ...
It'd be good to know why any of this was needed I guess.
johannes
next prev parent reply other threads:[~2026-11-10 20:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 7:58 [PATCH wireless-next v4 00/21] wifi: Add Seamless Mobility Domain (SMD) AP support Pooventhiran G
2026-11-06 7:58 ` [PATCH wireless-next v4 01/21] wifi: nl80211: define Seamless Mobility Domain (SMD) device capability Pooventhiran G
2026-11-10 14:15 ` Johannes Berg
2026-11-10 14:26 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 02/21] wifi: nl80211/cfg80211: define interfaces for SMD setup and STA update Pooventhiran G
2026-11-10 18:18 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 03/21] wifi: nl80211: add SMD BSS Transition sub-state STA flags Pooventhiran G
2026-11-10 18:27 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 04/21] wifi: cfg80211: define layouts for SMD BSS Transition context Pooventhiran G
2026-11-10 18:39 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 05/21] wifi: nl80211: define interfaces for SMD BSS Transition context transfer Pooventhiran G
2026-11-10 18:45 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 06/21] wifi: ieee80211: define APIs for UHR Link Reconfiguration frame checks Pooventhiran G
2026-11-06 7:58 ` [PATCH wireless-next v4 07/21] wifi: ieee80211: define API to check if frame is class 3 Pooventhiran G
2026-11-06 7:58 ` [PATCH wireless-next v4 08/21] wifi: nl80211/cfg80211: pack SMD dynamic context along with frame Pooventhiran G
2026-11-10 18:51 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 09/21] wifi: nl80211/cfg80211: add support for SMD context programming Pooventhiran G
2026-11-10 18:55 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 10/21] wifi: nl80211/cfg80211: add support for querying SMD context for target AP MLD Pooventhiran G
2026-11-10 19:00 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 11/21] wifi: nl80211/cfg80211: define API to notify SMD Drain completion Pooventhiran G
2026-11-10 19:01 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 12/21] wifi: mac80211: set SMD parameters for AP setup and STA update Pooventhiran G
2026-11-06 7:58 ` [PATCH wireless-next v4 13/21] wifi: mac80211: apply SMD BSS Transition STA sub-states Pooventhiran G
2026-11-10 20:29 ` Johannes Berg [this message]
2026-11-06 7:58 ` [PATCH wireless-next v4 14/21] wifi: mac80211: add driver_op for SMD substate changes Pooventhiran G
2026-11-10 20:38 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 15/21] wifi: mac80211: filter uplink and downlink frames based on SMD states Pooventhiran G
2026-11-06 7:58 ` [PATCH wireless-next v4 16/21] wifi: mac80211: send BlockAck policy in AMPDU action Pooventhiran G
2026-11-10 20:43 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 17/21] wifi: mac80211: pass rx_data directly from ieee80211_rx_list() Pooventhiran G
2026-11-06 7:58 ` [PATCH wireless-next v4 18/21] wifi: mac80211: handle UHR Link Reconfiguration frame Pooventhiran G
2026-11-06 7:58 ` [PATCH wireless-next v4 19/21] wifi: mac80211: add mac80211 support to handle NL80211_CMD_SET_SMD_CTX Pooventhiran G
2026-11-06 7:58 ` [PATCH wireless-next v4 20/21] wifi: mac80211: add mac80211 support to handle NL80211_CMD_GET_SMD_CTX Pooventhiran G
2026-11-10 20:47 ` Johannes Berg
2026-11-06 7:58 ` [PATCH wireless-next v4 21/21] wifi: mac80211: define API to invoke SMD Drain Completion event Pooventhiran G
2026-11-10 20:49 ` Johannes Berg
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=f4164ec832b8dab5da90ddccc527ddcae74a44c3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pooventhiran.g@oss.qualcomm.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
all inboxes | Powered by JetHome®