From: Janne Grunau <j@jannau.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
Hante Meuleman <meuleman@broadcom.com>,
"Gautam Shukla (Gautam Kumar)" <gautams@broadcom.com>,
Kalle Valo <kvalo@kernel.org>,
Pieter-Paul Giesberts <pieterpg@broadcom.com>,
Jason Huang <jason.huang2@infineon.com>,
linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com, asahi@lists.linux.dev,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] wifi: brcmfmac: cfg80211: Report port_authorized for 4-way HS offload
Date: Tue, 15 Sep 2026 21:05:27 +0200 [thread overview]
Message-ID: <20260915190527.GA212312@robin.jannau.net> (raw)
In-Reply-To: <3422e0b3b7d4889d2a728c41b0b02f6c80fa71bf.camel@sipsolutions.net>
On Tue, Sep 15, 2026 at 03:22:50PM +0200, Johannes Berg wrote:
> On Sat, 2026-09-12 at 11:40 +0200, Janne Grunau wrote:
> >
> > This will conflict with the "brcmfmac: add FT/OKC roaming offload
> > support" [3] series but is written in a way to easily resolve the
> > conflicts.
>
> I ... no, I'm not going to take that conflict, and I applied the FT/OKC
> series to wireless-next. Please create this patch on top of wireless-
> next, if needed at all, and then you can backport something later to
> stable if needed.
That is very unfortunate. I hoped this change could merged as a fix for
7.3.
The change is required. wpa_supplicant 2.12 (and unpatched 2.11) will
run into its authentication timeout and disconnect WPA2/3 PSK networks
on brcmfmac devices with firmware offload support.
I'll rebase onto wireless-next and send a v2 but I think it's serious
issue in the process that it will take until after v7.4-rc1 (7+ weeks
from now) before this fix will land in stable kernel releases.
Janne
next prev parent reply other threads:[~2026-09-15 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 9:40 Janne Grunau
2026-09-14 20:04 ` Arend van Spriel
2026-09-15 13:22 ` Johannes Berg
2026-09-15 19:05 ` Janne Grunau [this message]
2026-09-16 8:32 ` Johannes Berg
2026-09-16 9:32 ` Janne Grunau
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=20260915190527.GA212312@robin.jannau.net \
--to=j@jannau.net \
--cc=arend.vanspriel@broadcom.com \
--cc=asahi@lists.linux.dev \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=gautams@broadcom.com \
--cc=jason.huang2@infineon.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.com \
--cc=pieterpg@broadcom.com \
--cc=stable@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
all inboxes | Powered by JetHome®