From: Seth Forshee <seth.forshee@canonical.com>
To: wireless-regdb@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: [ANN] wireless-regdb: master-2019-03-01
Date: Fri, 1 Mar 2019 15:37:54 -0600 [thread overview]
Message-ID: <20190301213754.GH22074@ubuntu-xps13> (raw)
A new release of wireless-regdb (master-2019-03-01) is available at:
https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2019.03.01.tar.gz
The short log of changes since the 2018-10-24 release is below.
Thanks,
Seth
---
Chaitanya Tata (1):
wireless-regdb: update 60ghz band rules for us
Felix Fietkau (1):
wireless-regdb: Sync IN with G.S.R. 1048(E), October 2018
Peter Lundkvist (1):
wireless-regdb: Update regulatory rules for Sweden (SE) on 2.4/5/60 GHz
Rui Salvaterra (1):
wireless-regdb: Add 5725-5875 MHz rule for Portugal (PT)
Seth Forshee (1):
wireless-regdb: update regulatory database based on preceding changes
Xose Vazquez Perez (2):
wireless-regdb: delete outdated comment for DE
wireless-regdb: add URLs in README
reply other threads:[~2019-03-01 21:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190301213754.GH22074@ubuntu-xps13 \
--to=seth.forshee@canonical.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