From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Jason Huang <Jason.Huang2@infineon.com>, linux-wireless@vger.kernel.org
Cc: johannes.berg@intel.com, johannes@sipsolutions.net,
hsin-hung.li@cypress.com, linux-kernel@vger.kernel.org,
brcm80211@lists.linux.dev, brcm80211-dev-list.pdl@broadcom.com,
wlan-kernel-dev-list@infineon.com, jeff.johnson@oss.qualcomm.com,
Carella Chen <carella.chen@infineon.com>
Subject: Re: [PATCH v5 0/5] brcmfmac: add FT/OKC roaming offload support
Date: Sat, 22 Aug 2026 20:26:52 +0200 [thread overview]
Message-ID: <cbb4b486-c7db-4687-a08c-1b1486583d32@broadcom.com> (raw)
In-Reply-To: <71261493-e974-4f5c-a453-b4c2e449baf5@broadcom.com>
On 22/08/2026 20:24, Arend van Spriel wrote:
> On 21/08/2026 09:56, Jason Huang wrote:
>> From: Carella Chen <carella.chen@infineon.com>
>>
>> This series adds the cfg80211/nl80211 and brcmfmac pieces needed to
>> support firmware-assisted FT/OKC roaming offload.
>>
>> Patch 1 adds an nl80211 extended feature bit so drivers can advertise
>> roaming PMK programming support without claiming full 802.1X 4-way
>> handshake offload. The brcmfmac patches then detect firmware FBT/OKC
>> capabilities, keep roaming-offload connections in a firmware-supplicant
>> profile state, program PMK material for FT/OKC roaming, report port
>> authorization after offloaded roaming, and advertise the new capability
>> when firmware support is present.
>>
>> Changes in v5:
>> - Reworked nl80211_set_pmk() to avoid the 80-column checkpatch warning
>> on the 4-way handshake extended-feature check.
>> - Added kernel-doc for the brcmfmac OKC profile state added by the PMK
>> programming patch.
>> - Normalized Assisted-by trailers to the checkpatch-accepted
>> AGENT_NAME:MODEL_VERSION format.
>> - Added Johannes and the wireless/brcm80211 lists to the cover letter
>> Cc list for the nl80211 and brcmfmac changes.
>
> Hi Jason,
>
> Thanks for the follow-up, but looks like it happened again. Missing
> patch 5/5 as happened with v3 series.
I do have other comment(s) for v5 series, but feel free to send the
missing patch so I can review that in one go.
Regards,
Arend
next prev parent reply other threads:[~2026-08-22 18:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 7:56 [PATCH v5 0/5] brcmfmac: add FT/OKC roaming offload support Jason Huang
2026-08-21 7:56 ` [PATCH v5 1/5] wifi: nl80211: add roam offload extended feature Jason Huang
2026-08-22 18:36 ` Arend van Spriel
2026-08-30 9:14 ` Arend van Spriel
2026-09-01 7:14 ` HungTsung Huang
2026-09-01 8:56 ` Arend van Spriel
2026-09-04 8:38 ` Johannes Berg
2026-09-08 5:59 ` HungTsung Huang
2026-08-21 7:56 ` [PATCH v5 2/5] wifi: brcmfmac: detect firmware FBT and OKC support Jason Huang
2026-08-21 7:56 ` [PATCH v5 3/5] wifi: brcmfmac: add PMK programming for firmware roaming offload Jason Huang
2026-08-21 7:56 ` [PATCH v5 4/5] wifi: brcmfmac: report port authorization after offloaded roaming Jason Huang
2026-08-22 18:24 ` [PATCH v5 0/5] brcmfmac: add FT/OKC roaming offload support Arend van Spriel
2026-08-22 18:26 ` Arend van Spriel [this message]
2026-08-24 3:08 ` HungTsung Huang
2026-08-24 2:27 ` [PATCH v5 5/5] wifi: brcmfmac: advertise firmware roam " Jason Huang
2026-09-11 6:56 ` [PATCH v6 0/5] wifi: brcmfmac: add FT/OKC fast roaming " Jason Huang
2026-09-11 6:56 ` [PATCH v6 1/5] wifi: nl80211: add fast roam offload extended feature Jason Huang
2026-09-11 6:56 ` [PATCH v6 2/5] wifi: brcmfmac: detect firmware FBT and OKC support Jason Huang
2026-09-11 6:56 ` [PATCH v6 3/5] wifi: brcmfmac: add PMK programming for firmware roaming offload Jason Huang
2026-09-11 6:56 ` [PATCH v6 4/5] wifi: brcmfmac: report port authorization after offloaded roaming Jason Huang
2026-09-11 6:56 ` [PATCH v6 5/5] wifi: brcmfmac: advertise firmware fast roam offload support Jason Huang
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=cbb4b486-c7db-4687-a08c-1b1486583d32@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=Jason.Huang2@infineon.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=carella.chen@infineon.com \
--cc=hsin-hung.li@cypress.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wlan-kernel-dev-list@infineon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.