From: Jeff Johnson <jjohnson@kernel.org>
To: Raj Kumar Bhagat <raj.bhagat@oss.qualcomm.com>,
Jeff Johnson <jjohnson@kernel.org>, Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>,
Shayne Chen <shayne.chen@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
linux-kernel@vger.kernel.org, ath12k@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Sriram R <quic_srirrama@quicinc.com>
Subject: Re: [PATCH wireless-next 0/2] wifi: mac80211: fetch FILS and unsolicited probe response templates by link ID
Date: Fri, 20 Feb 2026 09:53:38 -0800 [thread overview]
Message-ID: <3b0d26bd-35ff-40af-af8e-fbc1dd0d31cd@kernel.org> (raw)
In-Reply-To: <20260220-fils-prob-by-link-v1-0-a2746a853f75@oss.qualcomm.com>
On 2/19/2026 11:42 AM, Raj Kumar Bhagat wrote:
> Currently, the FILS discovery and unsolicited probe response templates
> are always fetched from the default link of a virtual interface in both
> Multi-Link Operation (MLO) and non-MLO cases. However, in the MLO case
> there is a need to fetch these templates from a specific link instead of
> the default link.
>
> Hence, add support for fetching these templates based on the link ID from
> the corresponding link data.
>
> ---
> Sriram R (2):
> wifi: mac80211: fetch FILS discovery template by link ID
> wifi: mac80211: fetch unsolicited probe response template by link ID
>
> drivers/net/wireless/ath/ath11k/mac.c | 4 +--
> drivers/net/wireless/ath/ath12k/mac.c | 6 ++--
Acked-by: Jeff Johnson <jjohnson@kernel.org> # for drivers/net/wireless/ath
> drivers/net/wireless/mediatek/mt76/mt7915/mcu.c | 4 +--
> drivers/net/wireless/mediatek/mt76/mt7996/mcu.c | 6 ++--
> include/net/mac80211.h | 8 +++--
> net/mac80211/tx.c | 40 ++++++++++++++++---------
> 6 files changed, 44 insertions(+), 24 deletions(-)
> ---
> base-commit: 37a93dd5c49b5fda807fd204edf2547c3493319c
> change-id: 20260220-fils-prob-by-link-eef176414f1b
>
prev parent reply other threads:[~2026-02-20 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 19:42 [PATCH wireless-next 0/2] wifi: mac80211: fetch FILS and unsolicited probe response templates by link ID Raj Kumar Bhagat
2026-02-19 19:42 ` [PATCH wireless-next 1/2] wifi: mac80211: fetch FILS discovery template " Raj Kumar Bhagat
2026-02-19 19:42 ` [PATCH wireless-next 2/2] wifi: mac80211: fetch unsolicited probe response " Raj Kumar Bhagat
2026-02-20 17:53 ` Jeff Johnson [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=3b0d26bd-35ff-40af-af8e-fbc1dd0d31cd@kernel.org \
--to=jjohnson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=quic_srirrama@quicinc.com \
--cc=raj.bhagat@oss.qualcomm.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.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