Hi, Sorry about the delay.
> > > wdev->bss_type refers to the BSS that we are connecting/connected to > > > (Maybe rename to "conn_bss_type"?). > > > This member is used in sme.c. It was introduced because once the connect > > > is complete and driver calls cfg80211_connect_result(), cfg needs to find > > > the BSS being connected to. > > > > Ok I was thinking you were adding it to struct cfg80211_bss. Wouldn't that > > make a bit more sense? Of course it can also be derived from > > cfg80211_bss::channel and cfg80211_bss::capability, your call. > > > > However, it doesn't seem that you need it in wdev if you have it there > > inside wdev->current_bss? > > current_bss is set later. > > inside __cfg80211_connect_result(), we look for the BSS being connected to: > bss = cfg80211_get_bss(..., bssid, wdev->bss_type, ...) > only after that, current_bss is set to this BSS: > wdev->current_bss = bss_from_pub(bss); Ok. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
