From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: <johannes@sipsolutions.net>, <johannes@sipsolutions.net>,
<linville@tuxdriver.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
<linux-wireless@vger.kernel.org>
Subject: [PATCH 08/12] cfg80211: move check for ignore_reg_update() on wiphy_update_regulatory()
Date: Thu, 22 Jan 2009 15:05:50 -0800 [thread overview]
Message-ID: <1232665554-26132-9-git-send-email-lrodriguez@atheros.com> (raw)
In-Reply-To: <1232665554-26132-8-git-send-email-lrodriguez@atheros.com>
This ensures that the initial REGDOM_SET_BY_CORE upon wiphy registration
respects the wiphy->custom_regulatory setting. Without this and if OLD_REG
is disabled (which will be default soon as we remove it) the
wiphy->custom_regulatory is simply ignored.
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Acked-by: Johannes Berg <johannes@sipsolutions.net>
---
net/wireless/reg.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/net/wireless/reg.c b/net/wireless/reg.c
index 2a94dc0..a362c87 100644
--- a/net/wireless/reg.c
+++ b/net/wireless/reg.c
@@ -945,13 +945,15 @@ static void update_all_wiphy_regulatory(enum reg_set_by setby)
struct cfg80211_registered_device *drv;
list_for_each_entry(drv, &cfg80211_drv_list, list)
- if (!ignore_reg_update(&drv->wiphy, setby))
- wiphy_update_regulatory(&drv->wiphy, setby);
+ wiphy_update_regulatory(&drv->wiphy, setby);
}
void wiphy_update_regulatory(struct wiphy *wiphy, enum reg_set_by setby)
{
enum ieee80211_band band;
+
+ if (ignore_reg_update(wiphy, setby))
+ return;
for (band = 0; band < IEEE80211_NUM_BANDS; band++) {
if (wiphy->bands[band])
handle_band(wiphy, band);
--
1.6.1.rc3.51.g5832d
next prev parent reply other threads:[~2009-01-22 23:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 23:05 [PATCH 00/12] cfg80211/mac80211: few fixes/enhancements for regulatory Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 01/12] cfg80211: print correct intersected regulatory domain Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 02/12] cfg80211: add wiphy_apply_custom_regulatory() Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 03/12] cfg80211: export freq_reg_info() Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 04/12] cfg80211: Fix sanity check on 5 GHz when processing country IE Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 05/12] cfg80211: process user requests only after previous user/driver/core requests Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 06/12] cfg80211: ignore consecutive equal regulatory hints Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 07/12] cfg80211: rename fw_handles_regulatory to custom_regulatory Luis R. Rodriguez
2009-01-22 23:05 ` Luis R. Rodriguez [this message]
2009-01-22 23:05 ` [PATCH 09/12] cfg80211: pass more detailed regulatory request information on reg_notifier() Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 10/12] cfg80211: Allow for strict regulatory settings Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 11/12] mac80211: allow mac80211 drivers to get to struct ieee80211_hw from wiphy Luis R. Rodriguez
2009-01-22 23:05 ` [PATCH 12/12] cfg80211: allow users to help a driver's compliance Luis R. Rodriguez
2009-01-25 16:23 ` [PATCH 10/12] cfg80211: Allow for strict regulatory settings Johannes Berg
2009-01-25 16:24 ` [PATCH 00/12] cfg80211/mac80211: few fixes/enhancements for regulatory Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1232665554-26132-9-git-send-email-lrodriguez@atheros.com \
--to=lrodriguez@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox