All of lore.kernel.org
 help / color / mirror / Atom feed
From: Veerendranath Jakkam <quic_vjakkam@quicinc.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>, <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3] cfg80211: Increase akm_suites array size in cfg80211_crypto_settings
Date: Mon, 23 May 2022 18:57:36 +0530	[thread overview]
Message-ID: <12c8d629-86b0-1cd9-18f2-eeafccf36714@quicinc.com> (raw)
In-Reply-To: <a8a3b56b-5e82-28cb-bd61-e338bae25df2@quicinc.com>


On 5/20/2022 9:45 PM, Jeff Johnson wrote:
> On 5/19/2022 10:31 PM, Veerendranath Jakkam wrote:
>> Increase akm_suites array size in struct cfg80211_crypto_settings to 10
>> and advertise the capability to userspace. This allows userspace to send
>> more than two AKMs to driver in netlink commands such as
>> NL80211_CMD_CONNECT.
>>
>
> I have some grammar nits below...
>> This capability needed for implementing WPA3-Personal transition mode
>
> capability *is* needed
>
>> correctly with any driver that handles roaming internally. Currently,
>> the possible AKMs for multi-AKM connect can include PSK, PSK-SHA-256,
>> SAE, FT-PSK and FT-SAE since the count is already 5, Increasing
>
> ...and FT-SAE. Since the count is already 5, increasing...
>
>> the akm_suites array size to 10 should be reasonable for future
>> usecases.
>
> /jeff


Thanks Jeff. Fixed the suggested grammar nits in v5

--

veeru


  reply	other threads:[~2022-05-23 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  5:31 [PATCH v3] cfg80211: Increase akm_suites array size in cfg80211_crypto_settings Veerendranath Jakkam
2022-05-20 16:15 ` Jeff Johnson
2022-05-23 13:27   ` Veerendranath Jakkam [this message]
2022-05-23 13:31     ` Veerendranath Jakkam

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=12c8d629-86b0-1cd9-18f2-eeafccf36714@quicinc.com \
    --to=quic_vjakkam@quicinc.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_jjohnson@quicinc.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.