From: Seth Forshee <seth.forshee@canonical.com>
To: wireless-regdb@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, Atul Joshi <atul.suresh.joshi@gmail.com>
Subject: [PATCH] wireless-regdb: Add ETSI as the DFS region for Hong Kong
Date: Wed, 16 Sep 2015 09:22:00 -0500 [thread overview]
Message-ID: <1442413320-69656-1-git-send-email-seth.forshee@canonical.com> (raw)
Based on [1], Hong Kong follows ETSI requirements for DFS.
[1] http://www.ofca.gov.hk/filemanager/ofca/en/content_401/hkta1039.pdf
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
---
db.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/db.txt b/db.txt
index 982db34..d57ea84 100644
--- a/db.txt
+++ b/db.txt
@@ -490,7 +490,7 @@ country GY:
(2402 - 2482 @ 40), (30)
(5735 - 5835 @ 80), (30)
-country HK:
+country HK: DFS-ETSI
(2402 - 2482 @ 40), (20)
(5170 - 5250 @ 80), (17), AUTO-BW
(5250 - 5330 @ 80), (24), DFS, AUTO-BW
--
1.9.1
next reply other threads:[~2015-09-16 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 14:22 Seth Forshee [this message]
2015-09-23 16:21 ` [PATCH] wireless-regdb: Add ETSI as the DFS region for Hong Kong Seth Forshee
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=1442413320-69656-1-git-send-email-seth.forshee@canonical.com \
--to=seth.forshee@canonical.com \
--cc=atul.suresh.joshi@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wireless-regdb@lists.infradead.org \
/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