From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org,
wireless-regdb@lists.infradead.org,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [PATCH 7/7] wireless-regdb: optimize two of NL's rules
Date: Wed, 30 Oct 2013 22:45:09 +0100 [thread overview]
Message-ID: <1383169509-22619-8-git-send-email-mcgrof@do-not-panic.com> (raw)
In-Reply-To: <1383169509-22619-1-git-send-email-mcgrof@do-not-panic.com>
There's no reason not to merge these two rules.
This as picked up by the new CRDA optimizer.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
db.txt | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/db.txt b/db.txt
index efd9902..429a380 100644
--- a/db.txt
+++ b/db.txt
@@ -557,8 +557,7 @@ country MX: DFS-FCC
country NL: DFS-ETSI
(2402 - 2482 @ 40), (20)
- (5170 - 5250 @ 80), (20), NO-OUTDOOR
- (5250 - 5330 @ 80), (20), NO-OUTDOOR
+ (5170 - 5330 @ 80), (20), NO-OUTDOOR
(5490 - 5710 @ 80), (27), DFS
# 60 gHz band channels 1-4, ref: Etsi En 302 567
(57240 - 65880 @ 2160), (40), NO-OUTDOOR
--
1.8.4.rc3
next prev parent reply other threads:[~2013-10-30 21:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 21:45 [PATCH 0/7] wireless-regdb: DFS regions and optimizations Luis R. Rodriguez
2013-10-30 21:45 ` [PATCH 1/7] wireless-regdb: add DFS FCC regions Luis R. Rodriguez
2013-10-30 21:45 ` [PATCH 2/7] wireless-regdb: add DFS ETSI regions Luis R. Rodriguez
2013-10-30 21:45 ` [PATCH 3/7] wireless-regdb: add DFS JP regions Luis R. Rodriguez
2013-10-30 21:45 ` [PATCH 4/7] wireless-regdb: optimize two of DE's rules Luis R. Rodriguez
2013-10-30 21:45 ` [PATCH 5/7] wireless-regdb: optimize two of ES's rules Luis R. Rodriguez
2013-10-30 21:45 ` [PATCH 6/7] wireless-regdb: optimize two of IL's rules Luis R. Rodriguez
2013-10-30 21:45 ` Luis R. Rodriguez [this message]
2013-10-30 21:46 ` [PATCH 0/7] wireless-regdb: DFS regions and optimizations Luis R. Rodriguez
2013-11-01 13:28 ` 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=1383169509-22619-8-git-send-email-mcgrof@do-not-panic.com \
--to=mcgrof@do-not-panic.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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;
as well as URLs for NNTP newsgroup(s).