From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: linville@tuxdriver.com, johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [PATCH 3/6] ath: split user and driver reguluatory hint parsing
Date: Mon, 14 Oct 2013 17:42:08 -0700 [thread overview]
Message-ID: <1381797731-2454-4-git-send-email-mcgrof@do-not-panic.com> (raw)
In-Reply-To: <1381797731-2454-1-git-send-email-mcgrof@do-not-panic.com>
On the regulatory notifier split up the parsing of the
hints coming from drivers or user. We'll treat these
separately.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
drivers/net/wireless/ath/regd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/ath/regd.c b/drivers/net/wireless/ath/regd.c
index 8373650..7222eeb 100644
--- a/drivers/net/wireless/ath/regd.c
+++ b/drivers/net/wireless/ath/regd.c
@@ -422,6 +422,7 @@ void ath_reg_notifier_apply(struct wiphy *wiphy,
sizeof(struct ath_regulatory));
break;
case NL80211_REGDOM_SET_BY_DRIVER:
+ break;
case NL80211_REGDOM_SET_BY_USER:
break;
case NL80211_REGDOM_SET_BY_COUNTRY_IE:
--
1.8.4.rc3
next prev parent reply other threads:[~2013-10-15 0:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 0:42 [PATCH 0/6] ath / ath9k updates Luis R. Rodriguez
2013-10-15 0:42 ` [PATCH 1/6] cfg80211: export reg_initiator_name() Luis R. Rodriguez
2013-10-17 14:34 ` Johannes Berg
2013-10-18 18:01 ` John W. Linville
2013-10-18 18:21 ` Johannes Berg
2013-10-20 9:55 ` Luis R. Rodriguez
2013-10-15 0:42 ` [PATCH 2/6] ath: move common dynamic regulatory domain setting to a helper Luis R. Rodriguez
2013-10-15 0:42 ` Luis R. Rodriguez [this message]
2013-10-15 0:42 ` [PATCH 4/6] ath: add support for proper dynamic regulatory hints Luis R. Rodriguez
2013-10-15 0:42 ` [PATCH 5/6] ath9k: check for NULL rate when using ieee80211_get_rts_cts_rate() Luis R. Rodriguez
2013-10-15 0:42 ` [PATCH 6/6] ath9k: add TX99 support Luis R. Rodriguez
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=1381797731-2454-4-git-send-email-mcgrof@do-not-panic.com \
--to=mcgrof@do-not-panic.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;
as well as URLs for NNTP newsgroup(s).