From: Zhu Yi <yi.zhu@intel.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] cfg80211: add support for custom firmware regulatory solutions
Date: Mon, 10 Nov 2008 09:58:44 +0800 [thread overview]
Message-ID: <1226282324.2604.282.camel@debian.sh.intel.com> (raw)
In-Reply-To: <1226109668-13778-2-git-send-email-lrodriguez@atheros.com>
On Sat, 2008-11-08 at 10:01 +0800, Luis R. Rodriguez wrote:
> This adds API to cfg80211 to allow wireless drivers to inform
> us if their firmware can handle regulatory considerations *and*
> they cannot map these regulatory domains to an ISO / IEC 3166
> alpha2. In these cases we skip the first regulatory hint instead
> of expecting the driver to build their own regulatory structure,
> providing us with an alpha2, or using the reg_notifier().
>
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Thanks!
Acked-by: Zhu Yi <yi.zhu@intel.com>
-yi
next prev parent reply other threads:[~2008-11-10 1:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 2:01 [PATCH 0/2] Add reg options for intel regulatory Luis R. Rodriguez
2008-11-08 2:01 ` [PATCH 1/2] cfg80211: add support for custom firmware regulatory solutions Luis R. Rodriguez
2008-11-08 2:01 ` [PATCH 2/2] iwlwifi: enable custom fw regulatory solution Luis R. Rodriguez
2008-11-10 2:00 ` Zhu Yi
2008-11-10 1:58 ` Zhu Yi [this message]
2008-11-08 7:09 ` [PATCH 0/2] Add reg options for intel regulatory 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=1226282324.2604.282.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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).