On Thu, 2014-01-23 at 09:53 +0000, Mani, Raja wrote: > >Err, you failed to explain *why* this is a problem. I'm not even convinced you're right anyway. > To know match set count, nl80211 should count only NL80211_SCHED_*_ATTR_SSID. > Some cases, wpa_supplicant would pass NL80211_SCHED_*_ATTR_RSSI also alone with > NL80211_SCHED_*_ATTR_SSID. For example, assume one NL80211_SCHED_*_ATTR_SSID and > one NL80211_SCHED_*_ATTR_RSSI passed from wpa_supplicant. In this case, nl80211 count > NL80211_SCHED_*_ATTR_RSSI also one of the profile , Finally match set count will be come > 2 in this case. (Ideally, match set count should be 1). The same count value is passed to driver, > and driver also would assume there are two SSID available in match set array (request->match_sets). > But only one SSID is valid in request->match_sets array in this case. You still haven't explained *why* you think that a match set should only be considered to be one when it includes an SSID. That doesn't seem to be the definition of the API. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
