From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
wireless-regdb@lists.infradead.org
Subject: Re: wireless-regdb updated, please check!
Date: Fri, 11 Jan 2013 21:54:27 +0100 [thread overview]
Message-ID: <50F07C03.3050204@gmail.com> (raw)
John W. Linville wrote:
> I've been sitting on some wireless-regdb patches for some time.
> Mostly this is because I wasn't sure what to do with some/most of them.
> I even still have a few more like that...
>
> Anyway, I wanted to at least get the 60GHz bits out, and I pushed a
> few other changes as well. Please take a look, and let me know if
> I merged anything wrong or if there is still something missing.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-regdb.git
Did you forget CC:wireless-regdb@lists.infradead.org ?
How about these?
CEPT rules to ES:
http://lists.infradead.org/pipermail/wireless-regdb/2012-July/000073.html
http://lists.infradead.org/pipermail/wireless-regdb/2012-July/000074.html
http://lists.infradead.org/pipermail/wireless-regdb/2012-July/000075.html
WARNING: multiple messages have this Message-ID (diff)
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] wireless-regdb updated, please check!
Date: Fri, 11 Jan 2013 21:54:27 +0100 [thread overview]
Message-ID: <50F07C03.3050204@gmail.com> (raw)
John W. Linville wrote:
> I've been sitting on some wireless-regdb patches for some time.
> Mostly this is because I wasn't sure what to do with some/most of them.
> I even still have a few more like that...
>
> Anyway, I wanted to at least get the 60GHz bits out, and I pushed a
> few other changes as well. Please take a look, and let me know if
> I merged anything wrong or if there is still something missing.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-regdb.git
Did you forget CC:wireless-regdb@lists.infradead.org ?
How about these?
CEPT rules to ES:
http://lists.infradead.org/pipermail/wireless-regdb/2012-July/000073.html
http://lists.infradead.org/pipermail/wireless-regdb/2012-July/000074.html
http://lists.infradead.org/pipermail/wireless-regdb/2012-July/000075.html
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next reply other threads:[~2013-01-11 20:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 20:54 Xose Vazquez Perez [this message]
2013-01-11 20:54 ` [wireless-regdb] wireless-regdb updated, please check! Xose Vazquez Perez
2013-01-11 21:26 ` John W. Linville
2013-01-11 21:26 ` [wireless-regdb] " John W. Linville
2013-01-13 13:25 ` Xose Vazquez Perez
2013-01-13 13:25 ` [wireless-regdb] " Xose Vazquez Perez
2013-01-13 13:39 ` Xose Vazquez Perez
2013-01-13 13:39 ` [wireless-regdb] " Xose Vazquez Perez
2013-01-13 14:14 ` Arend van Spriel
2013-01-14 9:35 ` Xose Vazquez Perez
2013-01-14 9:35 ` Xose Vazquez Perez
2013-01-14 17:55 ` Arend van Spriel
2013-01-14 17:55 ` Arend van Spriel
-- strict thread matches above, loose matches on Subject: below --
2013-01-11 19:39 John W. Linville
2013-01-11 23:40 ` 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=50F07C03.3050204@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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.