From: "Bob Copeland" <me@bobcopeland.com>
To: "Pavel Roskin" <proski@gnu.org>
Cc: jirislaby@gmail.com, ath5k-devel@venema.h4ckr.net,
linux-wireless@vger.kernel.org, linville@tuxdriver.com,
michael+ath5k@stapelberg.de, linux-kernel@vger.kernel.org
Subject: Re: [ath5k-devel] [PATCH] ath5k: fix detection of jumbo frames
Date: Mon, 3 Nov 2008 09:26:24 -0500 [thread overview]
Message-ID: <b6c5339f0811030626rf9e7147peb1d4a2ca085bba@mail.gmail.com> (raw)
In-Reply-To: <1225719328.3575.9.camel@dv>
On Mon, Nov 3, 2008 at 8:35 AM, Pavel Roskin <proski@gnu.org> wrote:
> Thanks for catching it! Please mention rs_antenna in addition to
> rs_more.
>
>> - rs->rs_antenna = rx_status->rx_status_0 &
>> - AR5K_5210_RX_DESC_STATUS0_RECEIVE_ANTENNA;
>> - rs->rs_more = rx_status->rx_status_0 &
>> - AR5K_5210_RX_DESC_STATUS0_MORE;
>> + rs->rs_antenna = AR5K_REG_MS(rx_status->rx_status_0,
>> + AR5K_5210_RX_DESC_STATUS0_RECEIVE_ANTENNA);
>> + rs->rs_more = AR5K_REG_MS(rx_status->rx_status_0,
>> + AR5K_5210_RX_DESC_STATUS0_MORE);
>
> rs_more should be boolean. It would be better to use "!!" to calculate
> rs_rate. No need to shift anything. As for rs_antenna, it's fine with
^^^^^^
I assume you meant rs_more again: rs_more = !!(rx_status_0 & ...)
>> +#define AR5K_5212_RX_DESC_STATUS0_DECOMP_CRC_ERROR_S 13
>
> This doesn't belong to the patch. It looks like it's another boolean
> value, but it's not currently used.
ACK, all valid. I'll respin.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2008-11-03 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 19:08 [PATCH] ath5k: fix detection of jumbo frames Bob Copeland
2008-11-02 21:00 ` [ath5k-devel] " Luis R. Rodriguez
2008-11-02 21:52 ` Bob Copeland
2008-11-02 22:33 ` Luis R. Rodriguez
2008-11-03 2:44 ` Bob Copeland
2008-11-03 13:35 ` Pavel Roskin
2008-11-03 14:26 ` Bob Copeland [this message]
2008-11-03 14:40 ` [ath5k-devel] " Pavel Roskin
2008-11-04 3:14 ` [PATCH] ath5k: correct handling of rx status fields Bob Copeland
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=b6c5339f0811030626rf9e7147peb1d4a2ca085bba@mail.gmail.com \
--to=me@bobcopeland.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=michael+ath5k@stapelberg.de \
--cc=proski@gnu.org \
/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