From: Benjamin Berg <benjamin@sipsolutions.net>
To: Johannes Berg <johannes@sipsolutions.net>,
Michael Bommarito <michael.bommarito@gmail.com>,
linux-wireless@vger.kernel.org
Cc: Felix Fietkau <nbd@nbd.name>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Ramasamy Kaliappan <ramasamy.kaliappan@oss.qualcomm.com>
Subject: Re: [PATCH] wifi: mac80211: check ieee80211_rx_data_set_link return in pubsta MLO path
Date: Wed, 22 Apr 2026 10:17:14 +0200 [thread overview]
Message-ID: <3720de2882e8238855e85b312f66a39366068433.camel@sipsolutions.net> (raw)
In-Reply-To: <434407f50d6b7ee85ad14dd6db757f7d9f695a96.camel@sipsolutions.net> (sfid-20260422_082757_656444_8F0EBA32)
On Wed, 2026-04-22 at 08:27 +0200, Johannes Berg wrote:
> On Tue, 2026-04-21 at 20:06 -0400, Michael Bommarito wrote:
>
> > Benjamin Berg's 2026-02 RFC v2 "wifi: mac80211: refactor RX
> > link_id and station handling"
> > (20260223133818.9f5550ab445f.I...@changeid) touches the same
> > code and may supersede or subsume this patch; happy to fold /
> > rebase / drop.
>
> Yeah, Benjamin, what's up with that :)
Hmm, good question. I was hoping for a userspace hostap implementation
to start using the new NO_STA flag as that part is otherwise untested.
Qualcomm was going to work on that, but I have not yet heard about it
again.
That said, it should be fine to merge patches 1-4 at least. So I am
happy to submit them separately.
Benjamin
>
> OTOH we perhaps wants this patch in wireless, and then yours in
> wireless-next.
>
> johannes
prev parent reply other threads:[~2026-04-22 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 0:06 [PATCH] wifi: mac80211: check ieee80211_rx_data_set_link return in pubsta MLO path Michael Bommarito
2026-04-22 6:27 ` Johannes Berg
2026-04-22 8:17 ` Benjamin 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=3720de2882e8238855e85b312f66a39366068433.camel@sipsolutions.net \
--to=benjamin@sipsolutions.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michael.bommarito@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=ramasamy.kaliappan@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