linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Forshee <sforshee@kernel.org>
To: Sid Hayn <sidhayn@gmail.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] [ANN] wireless-regdb: master-2022-04-08
Date: Fri, 8 Apr 2022 11:05:42 -0500	[thread overview]
Message-ID: <YlBdVvV7NGNccysW@ubuntu-x1> (raw)
In-Reply-To: <CAM0KTbBCeyx8TGkGcNkjJ7TYjtr6zeFY2=1TWwbzd5d3xHdZXg@mail.gmail.com>

On Fri, Apr 08, 2022 at 11:37:54AM -0400, Sid Hayn wrote:
> Are "regulatory.db" and "regulatory.db.p7s" missing from this release
> on accident or no longer required?
> 
> I package wireless-regdb for gentoo but I honestly haven't been
> following development much more closely than just bumping for
> releases.  For the recent releases I've been installing regulatory.bin
> in /usr/lib/crda and regulatory.db and regulatory.db.p7s in
> /lib/firmware

Oops, it looks like a typo caused them to be removed by accident. I've
updated the archives and the signature to contain the missing files.
Thanks for letting me know!

Seth

> 
> Thanks,
> Zero_Chaos
> 
> On Fri, Apr 8, 2022 at 10:49 AM Seth Forshee <sforshee@kernel.org> wrote:
> >
> > A new release of wireless-regdb (master-2022-04-08) is available at:
> >
> > https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2022.04.08.tar.xz
> >
> > The short log of changes since the master-2022-02-18 release is below.
> >
> > Thanks,
> > Seth
> >
> > ---
> >
> > Richard Huynh (1):
> >       wireless-regdb: Update regulatory rules for Australia (AU)
> >
> > Roman Kunzman (1):
> >       wireless-regdb: Update regulatory rules for Israel (IL)
> >
> > Seth Forshee (2):
> >       wireless-regdb: add missing spaces for US S1G rules
> >       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

      parent reply	other threads:[~2022-04-08 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 14:48 [ANN] wireless-regdb: master-2022-04-08 Seth Forshee
     [not found] ` <CAM0KTbBCeyx8TGkGcNkjJ7TYjtr6zeFY2=1TWwbzd5d3xHdZXg@mail.gmail.com>
2022-04-08 16:05   ` Seth Forshee [this message]

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=YlBdVvV7NGNccysW@ubuntu-x1 \
    --to=sforshee@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sidhayn@gmail.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).