From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [ANN] wireless-regdb: master-2009-04-16
Date: Fri, 17 Apr 2009 14:07:56 -0400 [thread overview]
Message-ID: <20090417180755.GB3291@tuxdriver.com> (raw)
In-Reply-To: <E1Luqjw-00028y-LQ@sipsolutions.net>
People are reporting that regdbdump is failing to verify the signature
on regulatory.bin with this update, so you may want to hold-off...
John
On Fri, Apr 17, 2009 at 06:16:32PM +0200, wireless@sipsolutions.net wrote:
>
> A new release of wireless-regdb (master-2009-04-16) is available at:
>
> http://wireless.kernel.org/download/wireless-regdb/wireless-regdb-2009.04.16.tar.bz2
>
> SHA1 sum: 601001b97fe344fe64cdd3f9d0d80ddc9a729d02
>
>
> For your convenience the individual regulatory.bin file can be downloaded from:
>
> http://wireless.kernel.org/download/wireless-regdb/regulatory.bins/2009.04.16-regulatory.bin
>
> SHA1 sum eb35dd05a1d9a212fc76ef56f4da9bcdc59ba64a
>
> Here is the short log of the changes included in this
> release:
>
> John W. Linville - wireless-regdb: update regulatory.bin based on preceding changes.
> Luis R. Rodriguez - wireless-regdb: fix a couple of comment typos
> Luis R. Rodriguez - wireless-regdb: make distribution packaging easier
> Luis R. Rodriguez - wireless-regdb: KR few reg updates
> Luis R. Rodriguez - wireless-regdb: BN was missing two 5 GHz bands
> Johannes Berg - update/fix DE 5GHz rules
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-04-17 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 16:16 [ANN] wireless-regdb: master-2009-04-16 wireless
2009-04-17 18:07 ` John W. Linville [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=20090417180755.GB3291@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.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