cfg80211: put core regulatory request into queue
authorLuis R. Rodriguez <lrodriguez@atheros.com>
Thu, 18 Nov 2010 05:46:06 +0000 (21:46 -0800)
committerJohn W. Linville <linville@tuxdriver.com>
Mon, 22 Nov 2010 20:48:50 +0000 (15:48 -0500)
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>
net/wireless/reg.c

index 3be18d9a944f52479ed887dcea8ecaf81514d9a7..9830db61019ead8085636245c6997be2b3390f17 100644 (file)
@@ -1530,12 +1530,7 @@ static int regulatory_hint_core(const char *alpha2)
        request->alpha2[1] = alpha2[1];
        request->initiator = NL80211_REGDOM_SET_BY_CORE;
 
-       /*
-        * This ensures last_request is populated once modules
-        * come swinging in and calling regulatory hints and
-        * wiphy_apply_custom_regulatory().
-        */
-       reg_process_hint(request);
+       queue_regulatory_request(request);
 
        return 0;
 }