linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: wireless-regdb@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [ANN] wireless-regdb: master-2018-10-24
Date: Wed, 24 Oct 2018 08:31:12 -0600	[thread overview]
Message-ID: <20181024143112.GD8750@ubuntu-xps13> (raw)

A new release of wireless-regdb (master-2018-10-24) is available at:

https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2018.10.24.tar.gz

The short log of changes since the 2018-09-07 release is below.

Thanks,
Seth

---

Hauke Mehrtens (1):
      wireless-regdb: remove dependency to python attr

Seth Forshee (1):
      wireless-regdb: update regulatory database based on preceding changes

Sven Eckelmann (2):
      wireless-regdb: Sync FR with ETSI EN 301 893 V2.1.1 (2017-05)
      wireless-regdb: Sync DE with ETSI EN 301 893 V2.1.1 (2017-05)

                 reply	other threads:[~2018-10-24 14:31 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=20181024143112.GD8750@ubuntu-xps13 \
    --to=seth.forshee@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@do-not-panic.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).