Re: [PATCH V3 3/9] nl80211: add authorized flag to CONNECT event

2017-06-14 Thread Johannes Berg
> > So I was going to apply this, but now I'm no longer sure. > > Not sure if this means you can be convinced, but let me try anyway ;-) :-) > > First of all, I'm concerned it could confuse older tools that don't > > expect to see the notification twice. OTOH, they'd get the > > connected > > n

Re: [PATCH V3 3/9] nl80211: add authorized flag to CONNECT event

2017-06-14 Thread Arend van Spriel
On 6/13/2017 11:02 AM, Johannes Berg wrote: On Fri, 2017-06-09 at 13:08 +0100, Arend van Spriel wrote: When the driver supports offloading of the PTK/GTK handshakes completion of that during connect changes the layer 2 control port state to authorized. This patch allows the driver to pass that

Re: [PATCH V3 3/9] nl80211: add authorized flag to CONNECT event

2017-06-13 Thread Johannes Berg
On Fri, 2017-06-09 at 13:08 +0100, Arend van Spriel wrote: > When the driver supports offloading of the PTK/GTK handshakes > completion of that during connect changes the layer 2 control > port state to authorized. This patch allows the driver to pass > that state in cfg80211_connect_done() resulti

[PATCH V3 3/9] nl80211: add authorized flag to CONNECT event

2017-06-09 Thread Arend van Spriel
When the driver supports offloading of the PTK/GTK handshakes completion of that during connect changes the layer 2 control port state to authorized. This patch allows the driver to pass that state in cfg80211_connect_done() resulting in adding the new flag NL80211_ATTR_PORT_AUTHORIZED in the NL802