linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: wireless-regdb@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
	Seth Forshee <seth.forshee@canonical.com>,
	"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: new regulatory database mainteiner -- Seth Forshee
Date: Thu, 4 Dec 2014 14:59:46 -0500	[thread overview]
Message-ID: <20141204195945.GC2842@tuxdriver.com> (raw)

Greetings,

As you may know, I have been maintaining the wireless regulatory rules
database used by CRDA since the project was started.  Although I
am not an expert on regulatory law by anyone's estimation, I have
maintained this database both through personal trust in those
presenting patches and through an abundance of caution about only
applying non-controversial changes.

In any case, I now find other demands on my time.  I have asked Seth
Forshee if he would be willing to accept this responsibility from
me and Seth has graciously done so.  Seth, Luis, and I have been in
the process of making the actual technical hand-off over the past
several days, and I think everything should be in place soon (if it
isn't already there now).  This includes ensuring that Seth has the
necessary access for publishing wireless-regdb updates on kernel.org,
and ensuring that his public signing key is included as part of the
CRDA package distribution.

I would like to thank Seth for taking this important duty upon himself
and I wish him all the best in doing so.  I hope that everyone else
will do the same!

Thanks,

John
-- 
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:[~2014-12-04 20:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20141204195945.GC2842@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@suse.com \
    --cc=seth.forshee@canonical.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).