From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Frans Pop <elendil@planet.nl>,
Chris Clayton <chris2553@googlemail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ath5k - strange regulatory domain change
Date: Fri, 7 Aug 2009 14:00:33 -0400 [thread overview]
Message-ID: <20090807180033.GH7545@tuxdriver.com> (raw)
In-Reply-To: <43e72e890908071051w1f306349rfab32de80759006e@mail.gmail.com>
On Fri, Aug 07, 2009 at 10:51:17AM -0700, Luis R. Rodriguez wrote:
> On Fri, Aug 7, 2009 at 10:39 AM, Frans Pop<elendil@planet.nl> wrote:
> > Probably the simplest option would be to just display some identification
> > of the domain group itself and point users to documentation which
> > explains what countries fall under what groups. That would at least avoid
> > the confusion caused by randomly picking a matching country.
> > Variation could be to display the country if the group only contains one
> > country, but that could also be considered an inconsistent user
> > interface.
>
> Or maybe see if the currently set regulatory domain matches an alpha2
> in the group, if so then just display the same alpha2. Will take a
> look.
That makes sense to me...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-08-07 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 10:50 ath5k - strange regulatory domain change Chris Clayton
2009-08-07 11:24 ` Frans Pop
2009-08-07 12:56 ` Chris Clayton
2009-08-07 13:48 ` John W. Linville
2009-08-07 14:57 ` Chris Clayton
2009-08-07 15:16 ` John W. Linville
2009-08-07 17:13 ` Luis R. Rodriguez
2009-08-07 17:39 ` Frans Pop
2009-08-07 17:51 ` Luis R. Rodriguez
2009-08-07 18:00 ` John W. Linville [this message]
2009-08-07 15:35 ` Frans Pop
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=20090807180033.GH7545@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=chris2553@googlemail.com \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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 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.