From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: new regdb file format
Date: Mon, 19 Oct 2015 13:31:23 +0200 [thread overview]
Message-ID: <1445254283.3307.0.camel@sipsolutions.net> (raw)
In-Reply-To: <CAB3XZEdkpYrLXh1yTJCGA-ZGS0eRuqUhTwnD9WgZaw_g7UvioA@mail.gmail.com> (sfid-20151019_132848_630124_ACF93C4B)
On Mon, 2015-10-19 at 14:28 +0300, Eliad Peller wrote:
> while at it - is there any way to indicate exclusion of some
> channels?
> e.g. channels 38/42 in US (the current rule is "(5170 - 5250 @ 40)",
> which doesn't seem to forbid them)
>
Hm? Why would you want to do that, if you are allowed to use that band?
johannes
next prev parent reply other threads:[~2015-10-19 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 20:52 new regdb file format Johannes Berg
2015-10-14 21:01 ` Johannes Berg
2015-10-14 21:04 ` Johannes Berg
2015-10-19 11:28 ` Eliad Peller
2015-10-19 11:31 ` Johannes Berg [this message]
2015-10-19 11:52 ` Eliad Peller
2015-10-19 11:53 ` Johannes Berg
2015-10-19 11:59 ` Eliad Peller
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=1445254283.3307.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eliad@wizery.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
/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).