From: "John W. Linville" <linville@tuxdriver.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: linux-wireless@vger.kernel.org, Tomas Winkler <tomas.winkler@intel.com>
Subject: Re: [PATCH 3/7] iwlwifi: scan correct setting of valid rx_chains
Date: Mon, 6 Oct 2008 17:16:26 -0400 [thread overview]
Message-ID: <20081006211626.GJ3448@tuxdriver.com> (raw)
In-Reply-To: <1223280333-4383-4-git-send-email-yi.zhu@intel.com>
On Mon, Oct 06, 2008 at 04:05:29PM +0800, Zhu Yi wrote:
> From: Tomas Winkler <tomas.winkler@intel.com>
>
> This patch sets rx_chain bitmap correctly according hw configuration.
I guess this description is OK...I'm sure you can do better.
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-10-06 21:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 8:05 [PATCH 0/7] iwlwifi driver 10/06 updates Zhu Yi
2008-10-06 8:05 ` [PATCH 1/7] iwlwifi: make initial calibration set configurable Zhu Yi
2008-10-06 8:05 ` [PATCH 2/7] iwlwifi: fix ct kill configuration for 5350 Zhu Yi
2008-10-06 8:05 ` [PATCH 3/7] iwlwifi: scan correct setting of valid rx_chains Zhu Yi
2008-10-06 8:05 ` [PATCH 4/7] iwlwifi: scan fix comment Zhu Yi
2008-10-06 8:05 ` [PATCH 5/7] iwlwifi: take a valid antenna upon rate scale init Zhu Yi
2008-10-06 8:05 ` [PATCH 6/7] iwlwifi: remove STATUS_CONF_PENDING in scanning Zhu Yi
2008-10-06 8:05 ` [PATCH 7/7] iwlwifi: refactor rxon time command Zhu Yi
2008-10-06 21:30 ` John W. Linville
2008-10-06 21:25 ` [PATCH 5/7] iwlwifi: take a valid antenna upon rate scale init John W. Linville
2008-10-06 21:39 ` Tomas Winkler
2008-10-06 21:42 ` John W. Linville
2008-10-06 21:16 ` [PATCH 4/7] iwlwifi: scan fix comment John W. Linville
2008-10-06 21:16 ` John W. Linville [this message]
2008-10-06 21:15 ` [PATCH 2/7] iwlwifi: fix ct kill configuration for 5350 John W. Linville
2008-10-06 21:12 ` [PATCH 1/7] iwlwifi: make initial calibration set configurable John W. Linville
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=20081006211626.GJ3448@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tomas.winkler@intel.com \
--cc=yi.zhu@intel.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).