From: Zhu Yi <yi.zhu@intel.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Kolekar, Abhijeet" <abhijeet.kolekar@intel.com>,
Dan Williams <dcbw@redhat.com>
Subject: Re: [PATCH] iwl3945: added channel sysfs entry
Date: Fri, 26 Sep 2008 13:44:26 +0800 [thread overview]
Message-ID: <1222407866.2510.542.camel@debian.sh.intel.com> (raw)
In-Reply-To: <43e72e890809252239g2a6207f9r581b970388d9df14@mail.gmail.com>
On Thu, 2008-09-25 at 23:39 -0600, Luis R. Rodriguez wrote:
>
> Yes, this detail of information was conveyed to me at OLS by Guy. This
> is why we decided to add support for letting the driver not pass an
> alpha2 but to just build the regulatory domain structure itself and
> pass it. I even provided an example of how to do this in the
> Documentation/networking/regulatory.txt and tested it myself.
>
> Essentially this was added with your drivers in mind :)
Thanks. We will work on this.
-yi
prev parent reply other threads:[~2008-09-26 5:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 5:57 [PATCH] iwl3945: added channel sysfs entry Zhu Yi
2008-09-24 5:57 ` [PATCH] iwlwifi: don't fail if scan is issued too early Zhu Yi
2008-09-24 8:44 ` [PATCH] iwl3945: added channel sysfs entry Johannes Berg
2008-09-24 10:52 ` Dan Williams
2008-09-25 7:34 ` Zhu Yi
2008-09-25 9:23 ` Johannes Berg
2008-09-25 11:04 ` Tomas Winkler
2008-09-25 11:21 ` Johannes Berg
2008-09-25 11:50 ` Tomas Winkler
2008-09-26 3:54 ` Zhu Yi
2008-09-26 4:13 ` Luis R. Rodriguez
2008-09-26 5:13 ` Zhu Yi
2008-09-26 5:16 ` Zhu Yi
2008-09-26 5:28 ` Zhu Yi
2008-09-26 5:39 ` Luis R. Rodriguez
2008-09-26 5:40 ` Luis R. Rodriguez
2008-09-26 5:44 ` Zhu Yi [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=1222407866.2510.542.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=abhijeet.kolekar@intel.com \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 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).