From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Michael Green <Michael.Green@atheros.com>,
David Quan <David.Quan@atheros.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Subject: Re: A mailing list for regulatory wireless-regdb changes
Date: Fri, 6 Aug 2010 12:32:59 -0700 [thread overview]
Message-ID: <AANLkTikx=k0-zLFq95xJMoY2vbg85q5JuXDAUE0XXiBc@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinQLcc9iwu9YSV64_JcmDLdg9bkkG7PHA17oSRW@mail.gmail.com>
On Thu, May 27, 2010 at 9:44 AM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Thu, May 27, 2010 at 8:43 AM, John W. Linville
> <linville@tuxdriver.com> wrote:
>> On Thu, May 27, 2010 at 04:34:12PM +0100, David Woodhouse wrote:
>>> On Thu, 2010-05-27 at 11:05 -0400, John W. Linville wrote:
>>> > On Thu, May 27, 2010 at 01:15:50AM -0700, Luis R. Rodriguez wrote:
>>> > > David, can I trouble you for a mailman wireless-regdb mailing list on
>>> > > infradead.org? This would be used by those who are not developers and
>>> > > do not need to be subscribed to linux-wireless. An example are
>>> > > regulatory guys at different companies and generally interested
>>> > > people/developers on the topic. This should hopefully accelerate the
>>> > > turn around time for reviewing of patches and also a good placeholder
>>> > > for us to go back and check the discussions that went on about this.
>>> >
>>> > Is this really necessary?
>>>
>>> Feel free not to use it :)
>>
>> Just hoping to avoid unnecessary confusion -- I suppose it is fine
>> if that is what people want...
>
> I do not know how else to help speed up review without having to wait
> for a intermediary delay of someone at a company forwarding some
> regulatory changes e-mail to a person who is supposed to review them.
> With the list we would have a direct way for people to communicate
> with the folks who do care about regulatory and who may have roles who
> do that.
>
> If people do not mind the constant "please give us a few days" e-mails
> then things work without the list but then we (at least Atheros) just
> need to make sure regulatory change e-mails do get to the proper folks
> for review because we (Atheros) is committed to reviewing these
> changes.
BTW I found a use for this list now, to archive some initial e-mails
from Michael / others regarding reguatory changes. This information
would need to be parsed and then submitted in patch form but it should
also provide us with a URL reference on a regulatory related mailing
list for some details for commits on wireless-regdb.
I'll try it out next and you guys tell me if its OK.
PS. I'll be subscribing a few of you guys to this list now :)
Luis
prev parent reply other threads:[~2010-08-06 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 8:15 A mailing list for regulatory wireless-regdb changes Luis R. Rodriguez
2010-05-27 15:05 ` John W. Linville
2010-05-27 15:34 ` David Woodhouse
2010-05-27 15:43 ` John W. Linville
2010-05-27 16:44 ` Luis R. Rodriguez
2010-08-06 19:32 ` Luis R. Rodriguez [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='AANLkTikx=k0-zLFq95xJMoY2vbg85q5JuXDAUE0XXiBc@mail.gmail.com' \
--to=mcgrof@gmail.com \
--cc=David.Quan@atheros.com \
--cc=Michael.Green@atheros.com \
--cc=dwmw2@infradead.org \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).