public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth@forshee.me>
To: wireless-regdb@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: [wireless-regdb] [PATCH] wireless-regdb: add missing spaces for US S1G rules
Date: Wed, 23 Mar 2022 14:41:34 -0500	[thread overview]
Message-ID: <20220323194134.169332-1-sforshee@kernel.org> (raw)

The rules lack spaces in the frequency range definition, which works
find for building the database but causes problems for some external
parsers. Add the missing spaces.

Signed-off-by: Seth Forshee <sforshee@kernel.org>
---
 db.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/db.txt b/db.txt
index d45ec082e7c4..5f2168d21222 100644
--- a/db.txt
+++ b/db.txt
@@ -1619,11 +1619,11 @@ country UG: DFS-FCC
 # set out in 47 CFR § 15.205. TODO: reenable and specify a safe TX power here.
 country US: DFS-FCC
 	# S1G Channel 1-3
-	(902-904 @ 2), (30)
+	(902 - 904 @ 2), (30)
 	# S1G Channel 5-35
-	(904-920 @ 16), (30)
+	(904 - 920 @ 16), (30)
 	# S1G Channel 37-51
-	(920-928 @ 8), (30)
+	(920 - 928 @ 8), (30)
 	(2400 - 2472 @ 40), (30)
 	# 5.15 ~ 5.25 GHz: 30 dBm for master mode, 23 dBm for clients
 	(5150 - 5250 @ 80), (23), AUTO-BW
-- 
2.32.0


_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb

             reply	other threads:[~2022-03-23 19:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 19:41 Seth Forshee [this message]
2022-04-01  2:39 ` [wireless-regdb] [PATCH] wireless-regdb: add missing spaces for US S1G rules 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=20220323194134.169332-1-sforshee@kernel.org \
    --to=seth@forshee.me \
    --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