linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org,
	Arend van Spriel <arend.vanspriel@broadcom.com>,
	Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [V3, 6/9] brcmfmac: support 4-way handshake offloading for WPA/WPA2-PSK
Date: Fri, 30 Jun 2017 06:24:02 +0000 (UTC)	[thread overview]
Message-ID: <20170630062403.1EAB760DDF@smtp.codeaurora.org> (raw)
In-Reply-To: <1497010130-16186-7-git-send-email-arend.vanspriel@broadcom.com>

Arend Van Spriel <arend.vanspriel@broadcom.com> wrote:

> From: Arend van Spriel <arend@broadcom.com>
> 
> The firmware may have supplicant code built-in. This is detected
> by the driver and indicated in the wiphy features flags. User-space
> can use this flag to determine whether or not to provide the
> pre-shared key material in the nl80211 CONNECT command.
> 
> Reviewed-by: Gautam (Gautam Kumar) Shukla <gautams@broadcom.com>
> Reviewed-by: Hante Meuleman <meuleman@broadcom.com>
> Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com>
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>

Really sorry, I forgot to include this in today's pull request. My excuse this
time is that I'm on vacation and not really at full speed :)

-- 
https://patchwork.kernel.org/patch/9778339/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  parent reply	other threads:[~2017-06-30  6:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09 12:08 [PATCH V3 0/9] nl80211: add support for PTK/GTK handshake offload Arend van Spriel
2017-06-09 12:08 ` [PATCH V3 1/9] cfg80211: support 4-way handshake offloading for WPA/WPA2-PSK Arend van Spriel
2017-06-09 12:08 ` [PATCH V3 2/9] cfg80211: support 4-way handshake offloading for 802.1X Arend van Spriel
2017-06-09 12:08 ` [PATCH V3 3/9] nl80211: add authorized flag to CONNECT event Arend van Spriel
2017-06-13  9:02   ` Johannes Berg
2017-06-14  9:14     ` Arend van Spriel
2017-06-14 20:28       ` Johannes Berg
2017-06-09 12:08 ` [PATCH V3 4/9] nl80211: add authorized flag to ROAM event Arend van Spriel
2017-06-09 12:08 ` [PATCH V3 5/9] nl80211: remove desciption about request from NL80211_CMD_ROAM Arend van Spriel
2017-06-09 12:08 ` [PATCH V3 6/9] brcmfmac: support 4-way handshake offloading for WPA/WPA2-PSK Arend van Spriel
2017-06-14  5:09   ` [V3, " Kalle Valo
2017-06-30  6:24   ` Kalle Valo [this message]
2017-06-30  6:42   ` Kalle Valo
2017-06-09 12:08 ` [PATCH V3 7/9] brcmfmac: support 4-way handshake offloading for 802.1X Arend van Spriel
2017-06-09 12:08 ` [PATCH V3 8/9] brcmfmac: switch to using cfg80211_connect_done() Arend van Spriel
2017-06-09 12:08 ` [PATCH V3 9/9] brcmfmac: provide port authorized state in CONNECT event Arend van Spriel
2017-06-13  9:05 ` [PATCH V3 0/9] nl80211: add support for PTK/GTK handshake offload Johannes Berg

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=20170630062403.1EAB760DDF@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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).