Linux wireless drivers development
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: wireless-regdb@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, "Karl Möller" <karl@excors.net>
Subject: Re: [PATCH] wireless-regdb: Update ZA rules for 5490-5710 MHz
Date: Tue, 13 Oct 2015 13:37:03 -0500	[thread overview]
Message-ID: <20151013183703.GA50632@ubuntu-hedt> (raw)
In-Reply-To: <1444053722-33852-1-git-send-email-seth.forshee@canonical.com>

On Mon, Oct 05, 2015 at 09:02:02AM -0500, Seth Forshee wrote:
> The Radio Frequency Spectrum Regulations 2015 [1] drops the
> requirement for DFS and TPC in the 5490-5710 MHz range. Update
> the database to remove DFS for this range and remove the 3dB drop
> in the transmit power limit for TPC.
> 
> [1] http://www.ellipsis.co.za/wp-content/uploads/2014/12/Radio-Frequency-Spectrum-Regulations-2015.pdf
> 
> Cc: Karl Möller <karl@excors.net>
> Signed-off-by: Seth Forshee <seth.forshee@canonical.com>

Applied.

      reply	other threads:[~2015-10-13 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 14:02 [PATCH] wireless-regdb: Update ZA rules for 5490-5710 MHz Seth Forshee
2015-10-13 18:37 ` 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=20151013183703.GA50632@ubuntu-hedt \
    --to=seth.forshee@canonical.com \
    --cc=karl@excors.net \
    --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