From: Seth Forshee <seth.forshee@canonical.com>
To: wireless-regdb@lists.infradead.org
Cc: mj888@mail.co.uk, linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] [PATCH] wireless-regdb: update 5725-5850 MHz rule for GB
Date: Tue, 6 Jul 2021 11:17:39 -0500 [thread overview]
Message-ID: <YOSCI2bhylSuW8GH@ubuntu-x1> (raw)
In-Reply-To: <20210608141341.86462-1-seth.forshee@canonical.com>
On Tue, Jun 08, 2021 at 09:13:41AM -0500, Seth Forshee wrote:
> Based on the latest IR 2030 update [1], update this range to cover
> 5725-5850 MHz rather than 5725-5875 MHz, increase the max EIRP to
> 200 mW, remove the DFS requirement, and add NO-OUTDOOR.
>
> [1] https://www.ofcom.org.uk/__data/assets/pdf_file/0028/84970/ir-2030.pdf
>
> Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
Applied.
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
prev parent reply other threads:[~2021-07-06 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 14:13 [wireless-regdb] [PATCH] wireless-regdb: update 5725-5850 MHz rule for GB Seth Forshee
2021-07-06 16:17 ` Seth Forshee [this message]
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=YOSCI2bhylSuW8GH@ubuntu-x1 \
--to=seth.forshee@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mj888@mail.co.uk \
--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