Searched hist:a1699b75a1db31a1da2f0fc610ee696d02a19280 (Results 1 – 4 of 4) sorted by relevance
| /linux/net/mac80211/ |
| H A D | scan.c | diff a1699b75a1db31a1da2f0fc610ee696d02a19280 Fri Jul 30 16:46:07 CEST 2010 Johannes Berg <johannes.berg@intel.com> mac80211: unify scan and work mutexes
Having both scan and work mutexes is not just
a bit too fine grained, it also creates issues
when there's code that needs both since they
then need to be acquired in the right order,
which can be hard to do.
Therefore, use just a single mutex for both.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
| H A D | main.c | diff a1699b75a1db31a1da2f0fc610ee696d02a19280 Fri Jul 30 16:46:07 CEST 2010 Johannes Berg <johannes.berg@intel.com> mac80211: unify scan and work mutexes
Having both scan and work mutexes is not just
a bit too fine grained, it also creates issues
when there's code that needs both since they
then need to be acquired in the right order,
which can be hard to do.
Therefore, use just a single mutex for both.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
| H A D | ieee80211_i.h | diff a1699b75a1db31a1da2f0fc610ee696d02a19280 Fri Jul 30 16:46:07 CEST 2010 Johannes Berg <johannes.berg@intel.com> mac80211: unify scan and work mutexes
Having both scan and work mutexes is not just
a bit too fine grained, it also creates issues
when there's code that needs both since they
then need to be acquired in the right order,
which can be hard to do.
Therefore, use just a single mutex for both.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
| H A D | mlme.c | diff a1699b75a1db31a1da2f0fc610ee696d02a19280 Fri Jul 30 16:46:07 CEST 2010 Johannes Berg <johannes.berg@intel.com> mac80211: unify scan and work mutexes
Having both scan and work mutexes is not just
a bit too fine grained, it also creates issues
when there's code that needs both since they
then need to be acquired in the right order,
which can be hard to do.
Therefore, use just a single mutex for both.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|