All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Farina <sidhayn@gmail.com>
To: wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] [ANN] wireless-regdb: master-2015-10-22
Date: Thu, 22 Oct 2015 12:58:56 -0400	[thread overview]
Message-ID: <562915D0.1050506@gmail.com> (raw)
In-Reply-To: <20151022152316.GA6944@ubuntu-xps13>

For automated testing, is there a way to test read the database to make
sure the key works and the db isn't corrupt? I read the docs but I don't
see anything like this.

Thank,
Zero_Chaos

On 10/22/2015 11:23 AM, Seth Forshee wrote:
> A new release of wireless-regdb (master-2015-10-22) is available at:
> 
> https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2015.10.22.tar.gz
> 
> The short log of changes since the 2015-10-13 release is below.
> 
> Thanks,
> Seth
> 
> ---
> 
> Andrej Vlasic (1):
>       wireless-regdb: Update regulatory rules for Croatia (HR)
> 
> Johannes Berg (1):
>       wireless-regdb: fix gHz to GHz
> 
> Jouni Malinen (1):
>       wireless-regdb: Add 160 MHz channel bandwidth for Greenland (GL)
> 
> Seth Forshee (1):
>       wireless-regdb: update regulatory.bin based on preceding changes
> 
> 
> _______________________________________________
> wireless-regdb mailing list
> wireless-regdb@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/wireless-regdb
> 

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


  reply	other threads:[~2015-10-22 16:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 15:23 [ANN] wireless-regdb: master-2015-10-22 Seth Forshee
2015-10-22 15:23 ` [wireless-regdb] " Seth Forshee
2015-10-22 16:58 ` Rick Farina [this message]
2015-10-22 18:11   ` Seth Forshee
2015-10-22 18:33     ` Rick Farina
2015-10-22 18:50       ` 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=562915D0.1050506@gmail.com \
    --to=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 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.