From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org
Subject: [ANN] wireless-regdb: master-2013-02-13
Date: Wed, 13 Feb 2013 15:05:58 -0500 [thread overview]
Message-ID: <20130213200557.GD2169@tuxdriver.com> (raw)
A new release of wireless-regdb (master-2013-02-13) is available at:
http://kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2013.02.13.tar.bz2
Here is the short log of the changes included since the 2013-02-13
release:
Johannes Berg (1):
regdb: allow 40 MHz on world roaming channels 12/13
John W. Linville (4):
wireless-regdb: update regulatory.bin based on preceding changes.
Add specific data for Serbia for the 2 GHz and 5 GHz bands.
Clean-up some whitespace damage that had crept into db.txt...
wireless-regdb: update regulatory.bin based on preceding changes.
Xose Vazquez Perez (3):
wireless-regdb: Update regulatory rules for ES (Spain) on 5GHz and 2.4GHz
wireless-regdb: Update regulatory rules for ES (Spain) on 5GHz and 2.4GHz
wireless-regdb: Update regulatory rules for ES (Spain) on 5GHz and 2.4GHz
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org
Subject: [wireless-regdb] [ANN] wireless-regdb: master-2013-02-13
Date: Wed, 13 Feb 2013 15:05:58 -0500 [thread overview]
Message-ID: <20130213200557.GD2169@tuxdriver.com> (raw)
A new release of wireless-regdb (master-2013-02-13) is available at:
http://kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2013.02.13.tar.bz2
Here is the short log of the changes included since the 2013-02-13
release:
Johannes Berg (1):
regdb: allow 40 MHz on world roaming channels 12/13
John W. Linville (4):
wireless-regdb: update regulatory.bin based on preceding changes.
Add specific data for Serbia for the 2 GHz and 5 GHz bands.
Clean-up some whitespace damage that had crept into db.txt...
wireless-regdb: update regulatory.bin based on preceding changes.
Xose Vazquez Perez (3):
wireless-regdb: Update regulatory rules for ES (Spain) on 5GHz and 2.4GHz
wireless-regdb: Update regulatory rules for ES (Spain) on 5GHz and 2.4GHz
wireless-regdb: Update regulatory rules for ES (Spain) on 5GHz and 2.4GHz
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next reply other threads:[~2013-02-13 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 20:05 John W. Linville [this message]
2013-02-13 20:05 ` [wireless-regdb] [ANN] wireless-regdb: master-2013-02-13 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=20130213200557.GD2169@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.