> > > > On Wed, Mar 05, 2014 at 09:20:07AM +0000, Grumbach, Emmanuel wrote: > > > > So I guess you want me to revert the code we currently have in > > > > ieee80211_rx_mgmt_beacon ;) Don't know really... If you are > > > > associated to an AP and hear its beacons / probe responses on > > > > another channel you really have a big problem in your radio? > > > > > > FWIW: this logic is there since: > > > > > > commit d91f36db51661018f6d54ff5966e283bcec4c545 > > > Author: Johannes Berg <johannes@xxxxxxxxxxxxxxxx> > > > Date: Thu Apr 16 13:17:26 2009 +0200 > > > > > > mac80211: implement beacon filtering in software > > > > The frequency related areas in this commit are in a location that has > > a clear comment about it being for the current BSS. Your patch did not > > look like it would be for that case. If it is, the commit log should really say > that clearly. > > > > V2 with a better commit log on the way - thanks! Seems that my patch is useless since the because will still be processed by the scan code even when we are associated. So my patch didn't change anything for probes from APs we are not associated to, but it didn't change anything for probes of our AP either... -- 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
