On Wed, 2016-02-24 at 11:04 +0100, Arend Van Spriel wrote:
> I actually do not see any NLA_NESTED attributes with an explicit
> length. As you mentioned the nla_parse() of the nested attribute will
> validate the length of the stream so no need to put that in the
> policy.
Right, I think what you
On 23-2-2016 21:52, Johannes Berg wrote:
> On Tue, 2016-02-23 at 21:46 +0100, Arend Van Spriel wrote:
>>
>>> Maybe we should be less specific here regarding the NLA_FLAG and
>>> say
>>> that it will contain attributes for each, indicating which
>>> behaviours
>>> are supported, and say there's
On Tue, 2016-02-23 at 21:46 +0100, Arend Van Spriel wrote:
>
> > Maybe we should be less specific here regarding the NLA_FLAG and
> > say
> > that it will contain attributes for each, indicating which
> > behaviours
> > are supported, and say there's behaviour-dependent data inside each
> > of
> >
On 23-2-2016 15:20, Johannes Berg wrote:
> On Wed, 2016-02-17 at 11:47 +0100, Arend van Spriel wrote:
>>
>> + * @NL80211_ATTR_BSS_SELECT: nested attribute for driver supporting the
>> + * BSS selection feature. When used with %NL80211_CMD_GET_WIPHY it contains
>> + * NLA_FLAG type according &
On Wed, 2016-02-17 at 11:47 +0100, Arend van Spriel wrote:
>
> + * @NL80211_ATTR_BSS_SELECT: nested attribute for driver supporting the
> + * BSS selection feature. When used with %NL80211_CMD_GET_WIPHY it contains
> + * NLA_FLAG type according &enum nl80211_bss_select_attr to indicate what
>
Introducing a new feature that the driver can use to
indicate the driver/firmware supports configuration of BSS
selection criteria upon CONNECT command. This can be useful
when multiple BSS-es are found belonging to the same ESS,
ie. Infra-BSS with same SSID. The criteria can then be used to
offloa
