From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>,
linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] [ANN] wireless-regdb: master-2014-05-19
Date: Wed, 11 Jun 2014 22:42:07 +0200 [thread overview]
Message-ID: <20140611204207.GD6042@wotan.suse.de> (raw)
In-Reply-To: <CALhHN=pEo5H4AnWpOAhPs8LyK35wyhGJyvHTrh12nauQ-tOpDg@mail.gmail.com>
On Wed, Jun 11, 2014 at 09:15:19PM +0200, Janusz Dziedzic wrote:
> On 19 May 2014 20:50, John W. Linville <linville@tuxdriver.com> wrote:
> > A new release of wireless-regdb (master-2014-05-19) is available at:
> >
> > http://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2014.05.19.tar.gz
> >
> > Here is the short log of the changes included since the 2013-11-27
> > release:
> >
> > Bjørn Mork (1):
> > wireless-regdb: update NO's regulatory rules
> >
> > Janusz Dziedzic (3):
> > wireless-regdb: allow max bandwidth to be AUTO calculated
> > wireless-regdb: set AUTO bandwidth for world regulatory
> This two above should not be merged. That was first version of auto
> bandwidth calculation, we skip :)
How about on CRDA? Can you check if I merged the wrong stuff as I already
pushed as well? This also currently breaks the parses are there is no
support for the auto stuff yet.
Luis
next prev parent reply other threads:[~2014-06-11 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 18:50 [ANN] wireless-regdb: master-2014-05-19 John W. Linville
2014-06-11 19:15 ` [wireless-regdb] " Janusz Dziedzic
2014-06-11 20:42 ` Luis R. Rodriguez [this message]
2014-06-12 5:01 ` Janusz Dziedzic
2014-06-13 19:25 ` John W. Linville
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=20140611204207.GD6042@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=janusz.dziedzic@tieto.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).