Linux wireless drivers development
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [ANN] wireless-regdb: master-2011-04-28
Date: Thu, 12 May 2011 09:21:47 -0400	[thread overview]
Message-ID: <20110512132146.GK2490@tuxdriver.com> (raw)
In-Reply-To: <E1QKMHu-0006wu-F9@sipsolutions.net>

Weird, this took a while...

On Thu, May 12, 2011 at 05:10:06AM +0200, wireless@sipsolutions.net wrote:
> 
> A new release of wireless-regdb (master-2011-04-28) is available at:
> 
> http://wireless.kernel.org/download/wireless-regdb/wireless-regdb-2011.04.28.tar.bz2
> 
> SHA1 sum: d45ba854cf111a7ea4c21fbda9b996f0e8942ceb
> 
> 
> For your convenience the individual regulatory.bin file can be downloaded from:
> 
> http://wireless.kernel.org/download/wireless-regdb/regulatory.bins/2011.04.28-regulatory.bin
> 
> SHA1 sum d4f67f7c76c7206034237aa7dc93370b052ca888
> 
> Here is the short log of the changes included in this 
> release:
> 
> Anne Marcel Roorda (1):
>       Update regulatory rules for Netherlands (NL)
> 
> Johannes Berg (1):
>       regdb: fix moinmoin plugin license
> 
> John W. Linville (1):
>       wireless-regdb: update regulatory.bin based on preceding changes.
> 
> --
> 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.

  reply	other threads:[~2011-05-12 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12  3:10 [ANN] wireless-regdb: master-2011-04-28 wireless
2011-05-12 13:21 ` John W. Linville [this message]
2011-05-12 13:34   ` Johannes Berg

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=20110512132146.GK2490@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