From: Sascha Hauer <s.hauer@pengutronix.de>
To: Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
Francesco Dolcini <francesco@dolcini.it>,
David Lin <yu-hao.lin@nxp.com>
Subject: Re: [PATCH] wifi: mwifiex: increase max_num_akm_suites
Date: Mon, 10 Jun 2024 09:27:55 +0200 [thread overview]
Message-ID: <Zmaq-4whltVgrzCz@pengutronix.de> (raw)
In-Reply-To: <171767674666.2401308.2539321240473169281.kvalo@kernel.org>
On Thu, Jun 06, 2024 at 12:25:48PM +0000, Kalle Valo wrote:
> Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> > The maximum number of AKM suites will be set to two if not specified by
> > the driver. Set it to CFG80211_MAX_NUM_AKM_SUITES to let userspace
> > specify up to ten AKM suites in the akm_suites array.
> >
> > Without only the first two AKM suites will be used, further ones are
> > ignored.
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>
> I assume you that you have also tested this on a real device, right?
Sure. It was tested with a MAYA-W161-00B module from u-blox with a IW416
chipset.
BTW I haven't mentioned this, but It fixes the same problem as mentioned here:
https://lore.kernel.org/linux-kernel/20240523081428.2852276-1-s.hauer@pengutronix.de/T/
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-06-10 7:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 13:01 [PATCH] wifi: mwifiex: increase max_num_akm_suites Sascha Hauer
2024-06-06 12:25 ` Kalle Valo
2024-06-10 7:27 ` Sascha Hauer [this message]
2024-06-11 13:12 ` Marcel Ziswiler
2024-06-12 13:03 ` s.hauer
2024-06-20 18:05 ` Brian Norris
2024-06-21 8:48 ` Sascha Hauer
2024-06-21 19:16 ` Brian Norris
2024-07-16 9:10 ` Sascha Hauer
2024-07-30 8:48 ` Kalle Valo
2024-08-04 8:54 ` Kalle Valo
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=Zmaq-4whltVgrzCz@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=briannorris@chromium.org \
--cc=francesco@dolcini.it \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).