From: Johannes Berg <johannes@sipsolutions.net>
To: Aloka Dixit <aloka.dixit@oss.qualcomm.com>,
linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
ath11k@lists.infradead.org
Cc: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>,
Muna Sinada <muna.sinada@oss.qualcomm.com>
Subject: Re: [PATCH v4 1/3] wifi: nl80211: add link id of transmitted profile for MLO MBSSID
Date: Wed, 12 Mar 2025 09:55:44 +0100 [thread overview]
Message-ID: <52beaa2c05c91590797cc1f53b779fca085c8850.camel@sipsolutions.net> (raw)
In-Reply-To: <20250310200237.652950-2-aloka.dixit@oss.qualcomm.com>
Hi Aloka, all,
> + * @NL80211_MBSSID_CONFIG_ATTR_TX_LINK_ID: Link ID of the transmitted profile.
> + * This parameter is mandatory if the transmitted profile is part of an MLD
> + * and the interface getting configured is a non-transmitted profile. For all
> + * other cases it will be ignored.
So I guess it's a question of what "the interface getting configured"
means, but I guess you could set up the transmitting interface?
> @@ -5561,6 +5563,18 @@ static int nl80211_parse_mbssid_config(struct wiphy *wiphy,
> }
>
> config->tx_wdev = tx_netdev->ieee80211_ptr;
> +
> + if (config->tx_wdev->valid_links) {
> + if (!tb[NL80211_MBSSID_CONFIG_ATTR_TX_LINK_ID])
> + return -ENOLINK;
> +
> + config->tx_link_id =
> + nla_get_u8(tb[NL80211_MBSSID_CONFIG_ATTR_TX_LINK_ID]);
> +
> + if (!(config->tx_wdev->valid_links &
> + BIT(config->tx_link_id)))
> + return -ENOLINK;
> + }
> } else {
> config->tx_wdev = dev->ieee80211_ptr;
> }
So shouldn't that be one layer out, so the link ID can also apply if no
interface index was given, i.e. we took the else branch? Seems like that
should be applicable, or is there a specific reason not to apply in that
case?
johannes
next prev parent reply other threads:[~2025-03-12 8:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 20:02 [PATCH v4 0/3] wifi: MBSSID support in MLO Aloka Dixit
2025-03-10 20:02 ` [PATCH v4 1/3] wifi: nl80211: add link id of transmitted profile for MLO MBSSID Aloka Dixit
2025-03-12 8:55 ` Johannes Berg [this message]
2025-03-13 22:59 ` Aloka Dixit
2025-03-22 9:04 ` Johannes Berg
2025-04-01 19:24 ` Aloka Dixit
2025-03-10 20:02 ` [PATCH v4 2/3] wifi: mac80211: restructure tx profile retrieval " Aloka Dixit
2025-03-10 20:02 ` [PATCH v4 3/3] wifi: ath12k: pass link_conf for tx_arvif retrieval Aloka Dixit
2025-03-10 20:06 ` Aloka Dixit
2025-03-10 23:18 ` Jeff Johnson
2025-03-11 16:45 ` Aloka Dixit
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=52beaa2c05c91590797cc1f53b779fca085c8850.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=aloka.dixit@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=muna.sinada@oss.qualcomm.com \
--cc=rameshkumar.sundaram@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