From: "John W. Linville" <linville@tuxdriver.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Zhu Yi <yi.zhu@intel.com>,
linux-wireless@vger.kernel.org,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Subject: Re: [PATCH 5/7] iwlwifi: take a valid antenna upon rate scale init
Date: Mon, 6 Oct 2008 17:42:20 -0400 [thread overview]
Message-ID: <20081006214220.GO3448@tuxdriver.com> (raw)
In-Reply-To: <1ba2fa240810061439x219f5c0l2223c85042b39cee@mail.gmail.com>
On Mon, Oct 06, 2008 at 11:39:49PM +0200, Tomas Winkler wrote:
> On Mon, Oct 6, 2008 at 11:25 PM, John W. Linville
> <linville@tuxdriver.com> wrote:
> >> diff --git a/drivers/net/wireless/iwlwifi/iwl-5000.c b/drivers/net/wireless/iwlwifi/iwl-5000.c
> >> index c1300fb..56a3f0c 100644
> >> --- a/drivers/net/wireless/iwlwifi/iwl-5000.c
> >> +++ b/drivers/net/wireless/iwlwifi/iwl-5000.c
> >> @@ -811,10 +811,14 @@ static int iwl5000_hw_set_hw_params(struct iwl_priv *priv)
> >>
> >> switch (priv->hw_rev & CSR_HW_REV_TYPE_MSK) {
> >> case CSR_HW_REV_TYPE_5100:
> >> + priv->hw_params.tx_chains_num = 1;
> >> + priv->hw_params.rx_chains_num = 2;
> >> + priv->hw_params.valid_tx_ant = ANT_B;
> >> + priv->hw_params.valid_rx_ant = ANT_AB;
> >> + break;
> >> case CSR_HW_REV_TYPE_5150:
> >> priv->hw_params.tx_chains_num = 1;
> >> priv->hw_params.rx_chains_num = 2;
> >> - /* FIXME: move to ANT_A, ANT_B, ANT_C enum */
> >> priv->hw_params.valid_tx_ant = ANT_A;
> >> priv->hw_params.valid_rx_ant = ANT_AB;
> >> break;
> >
> > Do you realize that both clauses are the same (i.e. there is no
> > functional change)? How is this useful?
>
> The change is tx_ant
Quite right.
> > You need to change the comment...
>
> Right
Thanks.
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:42 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 [this message]
2008-10-06 21:16 ` [PATCH 4/7] iwlwifi: scan fix comment John W. Linville
2008-10-06 21:16 ` [PATCH 3/7] iwlwifi: scan correct setting of valid rx_chains John W. Linville
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=20081006214220.GO3448@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.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).