Re: [PATCH] cfg80211: Advertise extended capabilities per interface type to userspace

On Fri, 2016-04-22 at 14:52 +, Kanchanapally, Vidyullatha wrote: >  > > So I'm thinking something like > > > > supported_on_all = iftype_ext_capab[0] > > for i in 1..num_iftype_ext_capab-1: > >    supported_on_all &= iftype_ext_capab[i] > > WARN_ON(wiphy->ext_capa_mask & ~supported_on_all)

RE: [PATCH] cfg80211: Advertise extended capabilities per interface type to userspace

; Malinen, Jouni <jo...@qca.qualcomm.com>; Hullur Subramanyam, Amarnath <amarn...@qca.qualcomm.com>; Undekari, Sunil Dutt <usd...@qti.qualcomm.com> Subject: Re: [PATCH] cfg80211: Advertise extended capabilities per interface type to userspace On Fri, 2016-04-15 at 16:57 +0530, K

Re: [PATCH] cfg80211: Advertise extended capabilities per interface type to userspace

On Fri, 2016-04-15 at 16:57 +0530, Kanchanapally, Vidyullatha wrote: >  > +struct wiphy_iftype_ext_capab { > + enum nl80211_iftype iftype; > + const u8 *ext_capab; > + const u8 *ext_capab_mask; > + u8 ext_capab_len; I think you should reuse the struct member names that we used

[PATCH] cfg80211: Advertise extended capabilities per interface type to userspace

From: "Kanchanapally, Vidyullatha" The driver extended capabilities may differ for different interface types which the userspace needs to know (for example the fine timing measurement initiator and responder bits might differ for a station and AP). Add a new nl80211