All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	Francesco Dolcini <francesco@dolcini.it>,
	Kalle Valo <kvalo@kernel.org>, David Lin <yu-hao.lin@nxp.com>
Subject: Re: [PATCH] wifi: mwifiex: increase max_num_akm_suites
Date: Thu, 20 Jun 2024 11:05:24 -0700	[thread overview]
Message-ID: <ZnRvZMQJUr4APwUU@google.com> (raw)
In-Reply-To: <20240530130156.1651174-1-s.hauer@pengutronix.de>

Hi Sascha,

On Thu, May 30, 2024 at 03:01:56PM +0200, Sascha Hauer 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>
> ---
> 
> Current wpa_supplicant/hostapd only put a maximum of two into the
> akm_suites array as well, a patch changing this can be found here:
> http://lists.infradead.org/pipermail/hostap/2024-May/042720.html

Thanks for the patches and research.

Possibly dumb question: what's unique about mwifiex here? Everything you
describe above sounds applicable to all drivers, IIUC, and I don't see
any other driver that touches max_num_akm_suites.

Brian

  parent reply	other threads:[~2024-06-20 18:05 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
2024-06-11 13:12     ` Marcel Ziswiler
2024-06-12 13:03       ` s.hauer
2024-06-20 18:05 ` Brian Norris [this message]
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=ZnRvZMQJUr4APwUU@google.com \
    --to=briannorris@chromium.org \
    --cc=francesco@dolcini.it \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --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 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.