From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Jithu Jance <jithu.jance@broadcom.com>
Cc: linux-wireless@vger.kernel.org, Eliad Peller <eliad@wizery.com>,
Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH] cfg80211: support 4-way handshake offloading for WPA/WPA2-PSK
Date: Thu, 23 Feb 2017 11:37:21 +0100 [thread overview]
Message-ID: <1487846241.18380.2.camel@sipsolutions.net> (raw)
In-Reply-To: <9b6de09f-d872-fd67-971a-6da369fefe1a@broadcom.com> (sfid-20170223_113633_280663_6FA7C88C)
> So the code in wpa_supplicant_event_assoc() is either lying or the
> assoc event should come after driver has completed successfully. To
> me it seems worth it to have NL80211_CMD_EAP_COMPLETED event carrying
> the result or indeed give the CONNECTED event later in the driver.
Sorry - need to look at this in more detail later.
But yes, we do give CONNECTED event later in the driver right now.
johannes
next prev parent reply other threads:[~2017-02-23 10:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 10:09 [PATCH] cfg80211: support 4-way handshake offloading for WPA/WPA2-PSK Johannes Berg
2017-02-21 10:32 ` Arend Van Spriel
2017-02-21 10:40 ` Johannes Berg
2017-02-21 11:34 ` Arend Van Spriel
2017-02-21 11:45 ` Arend Van Spriel
2017-02-21 11:46 ` Johannes Berg
2017-02-21 11:54 ` Arend Van Spriel
2017-02-28 11:06 ` Arend Van Spriel
2017-03-03 12:21 ` Johannes Berg
2017-03-03 12:47 ` Arend Van Spriel
2017-03-09 13:38 ` Arend Van Spriel
2017-03-14 13:52 ` Johannes Berg
2017-03-18 7:08 ` Arend Van Spriel
2017-02-21 12:37 ` Johannes Berg
2017-02-21 19:57 ` Arend Van Spriel
2017-02-22 12:24 ` Jithu Jance
2017-02-23 10:36 ` Arend Van Spriel
2017-02-23 10:37 ` Johannes Berg [this message]
2017-02-23 10:40 ` Arend Van Spriel
2017-02-23 10:56 ` Jithu Jance
2017-03-03 12:20 ` Johannes Berg
2017-03-03 12:44 ` Arend Van Spriel
2017-03-09 14:53 ` Jithu Jance
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=1487846241.18380.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=eliad@wizery.com \
--cc=j@w1.fi \
--cc=jithu.jance@broadcom.com \
--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).