From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
Ting-Ying Li <tingying.li@cypress.com>,
Ting-Ying Li <tingying.li@infineon.com>,
James Prestwood <prestwoj@gmail.com>
Subject: Re: [PATCH wireless-next 4/4] wifi: brcmfmac: Fix structure size for WPA3 external SAE
Date: Fri, 25 Apr 2025 10:52:49 +0200 [thread overview]
Message-ID: <18407c0c-bf4b-4bcc-b029-831c23a8bbdb@broadcom.com> (raw)
In-Reply-To: <c03e8384c0c1e338ee9e874780f684d45ce1f1e1.camel@sipsolutions.net>
On 4/25/2025 10:51 AM, Johannes Berg wrote:
> On Fri, 2025-04-25 at 10:49 +0200, Arend van Spriel wrote:
>>
>> Crap. Just sent v2 executing my plan as stated above. v3 or is the
>> mai..eh..custodian willing to fix it up?
>>
>
> I'd say yes, but honestly I'm not sure I will get around to it today,
> and will likely forget next week. Sorry.
no problem. Expect v3 soon ;-)
Gr. AvS
prev parent reply other threads:[~2025-04-25 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 19:42 [PATCH wireless-next 0/4] wifi: brcmfmac: external auth support for Infineon devices Arend van Spriel
2025-04-24 19:42 ` [PATCH wireless-next 1/4] wifi: brcmfmac: support per-vendor cfg80211 callbacks and firmware events Arend van Spriel
2025-04-24 19:42 ` [PATCH wireless-next 2/4] wifi: brcmfmac: make per-vendor event map const Arend van Spriel
2025-04-24 19:42 ` [PATCH wireless-next 3/4] wifi: brcmfmac: cyw: support external SAE authentication in station mode Arend van Spriel
2025-04-24 19:42 ` [PATCH wireless-next 4/4] wifi: brcmfmac: Fix structure size for WPA3 external SAE Arend van Spriel
2025-04-25 7:57 ` Arend van Spriel
2025-04-25 8:40 ` Johannes Berg
2025-04-25 8:49 ` Arend van Spriel
2025-04-25 8:51 ` Johannes Berg
2025-04-25 8:52 ` Arend van Spriel [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=18407c0c-bf4b-4bcc-b029-831c23a8bbdb@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=prestwoj@gmail.com \
--cc=tingying.li@cypress.com \
--cc=tingying.li@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.