From: Johannes Berg <johannes@sipsolutions.net>
To: Ryan Mounce <ryan@mounce.com.au>,
Seth Forshee <seth.forshee@canonical.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless-regdb: Update rules for Australia (AU) and add 60GHz rules
Date: Thu, 23 Feb 2017 06:58:45 +0100 [thread overview]
Message-ID: <1487829525.1956.2.camel@sipsolutions.net> (raw)
In-Reply-To: <CAN+fvRb8R_3QyrnFFp0gd8PCcFXwbitNyh8K=ONqbmsGTrBsHQ@mail.gmail.com> (sfid-20170223_001058_739420_4AD8E69A)
> The frequency ranges have been "rounded down" to conform with the
> apparent convention of only including ranges used by standard 802.11
> channels, rather than using the actual frequency ranges as has been
> done for some countries (and most 60GHz rules). My preference is the
> latter so that there is a clear correlation between the regdb and
> relevant documentation, and so that the regdb may become useful
> beyond 802.11. With your blessing as maintainer I will also make this
> change to the patch.
I think that's just an artifact of the original database source and
would also prefer the documented ranges to be used.
johannes
next prev parent reply other threads:[~2017-02-23 6:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 6:35 [PATCH] wireless-regdb: Update rules for Australia (AU) and add 60GHz rules Ryan Mounce
2017-02-18 20:45 ` Sebastian Gottschall
2017-02-19 0:01 ` Ryan Mounce
2017-02-19 12:16 ` Sebastian Gottschall
2017-02-19 12:36 ` Ryan Mounce
2017-02-22 21:30 ` Seth Forshee
2017-02-22 23:05 ` Ryan Mounce
2017-02-23 5:58 ` Johannes Berg [this message]
2017-02-23 13:01 ` Seth Forshee
2017-02-23 13:52 ` [PATCH v2] " Ryan Mounce
2017-02-23 15:35 ` Seth Forshee
2017-02-24 2:50 ` Ryan Mounce
2017-02-24 14:55 ` Seth Forshee
2017-02-25 3:10 ` [PATCH v3] " Ryan Mounce
2017-03-01 14:59 ` Seth Forshee
2017-03-07 13:11 ` 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=1487829525.1956.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ryan@mounce.com.au \
--cc=seth.forshee@canonical.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).