From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>, Jouni Malinen <j@w1.fi>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] cfg80211: add control port state to struct cfg80211_connect_resp_params
Date: Fri, 28 Apr 2017 14:02:03 +0200 [thread overview]
Message-ID: <1493380923.2431.13.camel@sipsolutions.net> (raw)
In-Reply-To: <c0b5817a-c4fa-8f7c-2632-cf22aa09d71b@broadcom.com> (sfid-20170426_204655_775269_D5AEED53)
> I tested the 4-way-hs (both Personal and 802.1X) with boolean
> parameter similar to what is proposed in the patch for roaming
> "cfg80211/nl80211: add authorized flag to roaming event" and it works
> fine. So I can extend it for use in connect result. Just had one
> issue regarding the type, ie. flag vs. u8 because of how things are
> done in wpa_supplicant supporting QCA roam+auth vendor-specific
> event.
Ok.
We have lots of related but somewhat conflicting things in flight right
now, and we need somebody to go collect them all into a consistent
patchset, preferably even with the 4-way-HS offload [1] thrown in. That
needs rebasing anyway because it introduces the _PMK attribute that
Jouni already added for FILS now.
Do you want to pick that up? I probably can't do it soon - I'm likely
busy with other things the next week or two, then travel again, ...
johannes
[1] https://patchwork.kernel.org/patch/9584201/
next prev parent reply other threads:[~2017-04-28 12:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 21:01 [RFC] cfg80211: add control port state to struct cfg80211_connect_resp_params Arend van Spriel
2017-04-25 14:40 ` Johannes Berg
2017-04-25 18:34 ` Arend Van Spriel
2017-04-25 18:36 ` Johannes Berg
2017-04-25 18:56 ` Arend Van Spriel
2017-04-26 7:20 ` Johannes Berg
2017-04-26 18:46 ` Arend Van Spriel
2017-04-28 12:02 ` Johannes Berg [this message]
2017-04-28 12:46 ` Arend Van Spriel
2017-04-28 12:53 ` 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=1493380923.2431.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=j@w1.fi \
--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 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.