From: "Arend van Spriel" <arend@broadcom.com>
To: "Xose Vazquez Perez" <xose.vazquez@gmail.com>
Cc: wireless-regdb@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [wireless-regdb] wireless-regdb updated, please check!
Date: Mon, 14 Jan 2013 18:55:43 +0100 [thread overview]
Message-ID: <50F4469F.3030407@broadcom.com> (raw)
In-Reply-To: <50F3D145.7060004@gmail.com>
On 01/14/2013 10:35 AM, Xose Vazquez Perez wrote:
> On 01/13/2013 03:14 PM, Arend van Spriel wrote:
>
>> On 01/13/2013 02:39 PM, Xose Vazquez Perez wrote:
>
>>> On 01/11/2013 10:26 PM, John W. Linville wrote:
>
>>>>> On Fri, Jan 11, 2013 at 09:54:27PM +0100, Xose Vazquez Perez wrote:
>>>>>>> Did you forget CC:wireless-regdb at lists.infradead.org ?
>
>>>>> Well, sorta...but I'm not sure that you can prove that anyone actually
>>>>> reads that list anyway... :-(
>>> 40 people:
>
>> I would put my money on it that most of those are also keeping taps on
>> the linux-wireless list. I know I do.
>
> If people believe wireless-regdb ml is superfluous, should it be
> removed ?
Not entirely what I said, but maybe John implied it. The added value of
it would be that regulatory patches are archived separately. I can see
that announcements are a gray area as you may want to reach a bigger crowd.
Gr. AvS
prev parent reply other threads:[~2013-01-14 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 20:54 wireless-regdb updated, please check! Xose Vazquez Perez
2013-01-11 21:26 ` John W. Linville
2013-01-13 13:25 ` Xose Vazquez Perez
2013-01-13 13:39 ` Xose Vazquez Perez
[not found] ` <50F2C154.2040807@broadcom.com>
2013-01-14 9:35 ` [wireless-regdb] " Xose Vazquez Perez
2013-01-14 17:55 ` Arend van Spriel [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=50F4469F.3030407@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wireless-regdb@lists.infradead.org \
--cc=xose.vazquez@gmail.com \
/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).