From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Kouhei Sutou <kou@clear-code.com>,
Stephen.Chen@atheros.com, David.Quan@atheros.com,
linux-wireless@vger.kernel.org, Michael.Green@atheros.com
Subject: Re: [PATCH] zd1211rw: ignore unknown regulatory domain.
Date: Wed, 16 Jun 2010 08:46:49 -0700 [thread overview]
Message-ID: <AANLkTikkZQa37Y3DTMQlb1mzYE7qN9hqABvU2Tvwuobq@mail.gmail.com> (raw)
In-Reply-To: <20100616152903.GA3138@tuxdriver.com>
On Wed, Jun 16, 2010 at 8:29 AM, John W. Linville
<linville@tuxdriver.com> wrote:
> On Thu, Jun 17, 2010 at 12:02:23AM +0900, Kouhei Sutou wrote:
>> Hi,
>>
>> In <20100616134421.GB2404@tuxdriver.com>
>> "Re: [PATCH] zd1211rw: ignore unknown regulatory domain." on Wed, 16 Jun 2010 09:44:22 -0400,
>> "John W. Linville" <linville@tuxdriver.com> wrote:
>>
>> > On Wed, Jun 16, 2010 at 09:55:23PM +0900, Kouhei Sutou wrote:
>> >
>> >> I used 'ZD_REGDOMAIN_JAPAN_GW_US54GXS' as a macro name for
>> >> 0x49 because 0x49 is used by GW-US54GXS. Is it OK? Or should
>> >> I use other name for it?
>> >
>> > Hopefully someone can suggest a better name. Anyone know what inspired
>> > "ZD_REGDOMAIN_JAPAN_ADD"?
>>
>> 'ZD_REGDOMAIN_JAPAN_3' was used in another patch:
>> https://patchwork.kernel.org/patch/47220/
>>
>> But I don't know why '3' was used...
>
> '3' makes sense to me. The better question is why not change 'ADD' to '2'? :-)
2 is fine to replace ADD, I think "ADD" is additional :P
Luis
next prev parent reply other threads:[~2010-06-16 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 5:52 [PATCH] zd1211rw: ignore unknown regulatory domain Kouhei Sutou
2010-06-13 20:23 ` Luis R. Rodriguez
2010-06-15 14:25 ` Kouhei Sutou
2010-06-15 15:22 ` Luis R. Rodriguez
2010-06-16 12:55 ` Kouhei Sutou
2010-06-16 13:44 ` John W. Linville
2010-06-16 15:02 ` Kouhei Sutou
2010-06-16 15:29 ` John W. Linville
2010-06-16 15:46 ` Luis R. Rodriguez [this message]
2010-06-15 17:40 ` Gábor Stefanik
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=AANLkTikkZQa37Y3DTMQlb1mzYE7qN9hqABvU2Tvwuobq@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=David.Quan@atheros.com \
--cc=Michael.Green@atheros.com \
--cc=Stephen.Chen@atheros.com \
--cc=kou@clear-code.com \
--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).