linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org
Subject: [ANN] wireless-regdb: master-2014-05-19
Date: Mon, 19 May 2014 14:50:47 -0400	[thread overview]
Message-ID: <20140519185046.GH7650@tuxdriver.com> (raw)

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
      wireless-regdb: add AUTO-BW rule flag

Johannes Berg (1):
      regdb: Republic of Korea: fix double rule

John W. Linville (2):
      wireless-regdb: correct some flag damage...
      wireless-regdb: update regulatory.bin based on preceding changes.

Luis R. Rodriguez (1):
      wireless-regdb: embrace the Developer Certificate of Origin for contributions

Ronald Wahl (1):
      wireless-regdb: add channels 52..64 and 100..144 to world regdom

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.


             reply	other threads:[~2014-05-19 19:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 18:50 John W. Linville [this message]
2014-06-11 19:15 ` [wireless-regdb] [ANN] wireless-regdb: master-2014-05-19 Janusz Dziedzic
2014-06-11 20:42   ` Luis R. Rodriguez
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=20140519185046.GH7650@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --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;
as well as URLs for NNTP newsgroup(s).