From: Kalle Valo <kvalo@kernel.org>
To: David Lin <yu-hao.lin@nxp.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
briannorris@chromium.org, francesco@dolcini.it,
tsung-hsien.hsieh@nxp.com, David Lin <yu-hao.lin@nxp.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v11 1/2] wifi: mwifiex: add host mlme for client mode
Date: Sun, 4 Aug 2024 08:56:31 +0000 (UTC) [thread overview]
Message-ID: <172276178982.2804131.7220003471537783365.kvalo@kernel.org> (raw)
In-Reply-To: <20240704033001.603419-2-yu-hao.lin@nxp.com>
David Lin <yu-hao.lin@nxp.com> wrote:
> Add host based MLME to enable WPA3 functionalities in client mode.
> This feature required a firmware with the corresponding V2 Key API
> support. The feature (WPA3) is currently enabled and verified only
> on IW416. Also, verified no regression with change when host MLME
> is disabled.
>
> Signed-off-by: David Lin <yu-hao.lin@nxp.com>
> Reviewed-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> Acked-by: Brian Norris <briannorris@chromium.org>
2 patches applied to wireless-next.git, thanks.
36995892c271 wifi: mwifiex: add host mlme for client mode
9588469d0697 wifi: mwifiex: add host mlme for AP mode
--
https://patchwork.kernel.org/project/linux-wireless/patch/20240704033001.603419-2-yu-hao.lin@nxp.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-08-04 8:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 3:29 [PATCH v11 0/2] wifi: mwifiex: add code to support host mlme David Lin
2024-07-04 3:30 ` [PATCH v11 1/2] wifi: mwifiex: add host mlme for client mode David Lin
2024-08-04 8:56 ` Kalle Valo [this message]
2024-07-04 3:30 ` [PATCH v11 2/2] wifi: mwifiex: add host mlme for AP mode David Lin
2024-07-08 19:26 ` Brian Norris
2024-07-09 2:26 ` [EXT] " David Lin
2024-07-10 1:47 ` [PATCH v11 0/2] wifi: mwifiex: add code to support host mlme David Lin
2024-07-10 8:02 ` Kalle Valo
2024-07-11 1:33 ` [EXT] " David Lin
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=172276178982.2804131.7220003471537783365.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=briannorris@chromium.org \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tsung-hsien.hsieh@nxp.com \
--cc=yu-hao.lin@nxp.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
all inboxes | Powered by JetHome®