cfg80211: put core regulatory request into queue
This will simplify the synchronization for pending requests. Without this we have a race between the core and when we restore regulatory settings, although this is unlikely its best to just avoid that race altogether. Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com> Tested-by: Mark Mentovai <mark@moxienet.com> Tested-by: Bruno Randolf <br1@einfach.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
This commit is contained in:
committed by
John W. Linville
parent
8ce4699995
commit
31e99729ae
@@ -1530,12 +1530,7 @@ static int regulatory_hint_core(const char *alpha2)
|
|||||||
request->alpha2[1] = alpha2[1];
|
request->alpha2[1] = alpha2[1];
|
||||||
request->initiator = NL80211_REGDOM_SET_BY_CORE;
|
request->initiator = NL80211_REGDOM_SET_BY_CORE;
|
||||||
|
|
||||||
/*
|
queue_regulatory_request(request);
|
||||||
* This ensures last_request is populated once modules
|
|
||||||
* come swinging in and calling regulatory hints and
|
|
||||||
* wiphy_apply_custom_regulatory().
|
|
||||||
*/
|
|
||||||
reg_process_hint(request);
|
|
||||||
|
|
||||||
return 0;
|
return 0;
|
||||||
}
|
}
|
||||||
|
Reference in New Issue
Block a user