Revision 1c430a727fa512500a422ffe4712166c550ea06a authored by Johannes Berg on 07 May 2012, 13:39:06 UTC, committed by David S. Miller on 07 May 2012, 23:21:29 UTC
Neither compare_ether_addr() nor compare_ether_addr_64bits() (as it can fall back to the former) have comparison semantics like memcmp() where the sign of the return value indicates sort order. We had a bug in the wireless code due to a blind memcmp replacement because of this. A cursory look suggests that the wireless bug was the only one due to this semantic difference. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>
1 parent 6eddcb4
Computing file changes ...
