From: Bob Copeland <me@bobcopeland.com>
To: Andrew Blaich <ablaich@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: [PATCH] ath5k: retries in ath5k_hw_setup_4word_tx_desc
Date: Tue, 16 Mar 2010 08:12:45 -0400 [thread overview]
Message-ID: <20100316121245.GC27463@hash.localnet> (raw)
In-Reply-To: <6b5e31691003151300h1ab71850g695cbec6cdbaa0a0@mail.gmail.com>
On Mon, Mar 15, 2010 at 04:00:49PM -0400, Andrew Blaich wrote:
> Removing AR5K_TUNE_HWTXTRIES from the Ath5k code, it adds 4
> retries to tx_tries0. By removing AR5K_TUNE_HWTXTRIES, the rate
> control algorithm is given full control over the retry count.
>
> Signed-off-by:: Andrew Blaich <ablaich@gmail.com>
I believe John has already picked up the patch into wireless-testing.
Thanks for the submission!
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2010-03-16 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 20:00 [PATCH] ath5k: retries in ath5k_hw_setup_4word_tx_desc Andrew Blaich
2010-03-16 12:12 ` Bob Copeland [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=20100316121245.GC27463@hash.localnet \
--to=me@bobcopeland.com \
--cc=ablaich@gmail.com \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=mickflemm@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).