All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <sforshee@kernel.org>
To: wireless-regdb@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: [ANN] wireless-regdb: master-2022-08-12
Date: Fri, 12 Aug 2022 10:53:11 -0500	[thread overview]
Message-ID: <YvZ3ZyPXvYdc8AYm@ubuntu-x1> (raw)

A new release of wireless-regdb (master-2022-08-12) is available at:

https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2022.08.12.tar.xz

The short log of changes since the master-2022-06-06 release is below.

Thanks,
Seth

---

Seth Forshee (3):
      wireless-regdb: add 5 GHz rules for GY
      wireless-regdb: update 5 GHz rules for PK and add 60 GHz rule
      wireless-regdb: update regulatory database based on preceding changes

WARNING: multiple messages have this Message-ID (diff)
From: Seth Forshee <sforshee@kernel.org>
To: wireless-regdb@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: [wireless-regdb] [ANN] wireless-regdb: master-2022-08-12
Date: Fri, 12 Aug 2022 10:53:11 -0500	[thread overview]
Message-ID: <YvZ3ZyPXvYdc8AYm@ubuntu-x1> (raw)

A new release of wireless-regdb (master-2022-08-12) is available at:

https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2022.08.12.tar.xz

The short log of changes since the master-2022-06-06 release is below.

Thanks,
Seth

---

Seth Forshee (3):
      wireless-regdb: add 5 GHz rules for GY
      wireless-regdb: update 5 GHz rules for PK and add 60 GHz rule
      wireless-regdb: update regulatory database based on preceding changes

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb


             reply	other threads:[~2022-08-12 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 15:53 Seth Forshee [this message]
2022-08-12 15:53 ` [wireless-regdb] [ANN] wireless-regdb: master-2022-08-12 Seth Forshee

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=YvZ3ZyPXvYdc8AYm@ubuntu-x1 \
    --to=sforshee@kernel.org \
    --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.