From: Bruno Randolf <br1@einfach.org>
To: Ben Greear <greearb@candelatech.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/6] ath9k: fix RX poison issue
Date: Fri, 22 Oct 2010 09:30:01 +0900 [thread overview]
Message-ID: <201010220930.01071.br1@einfach.org> (raw)
In-Reply-To: <4CC07CA9.4040808@candelatech.com>
On Fri October 22 2010 02:47:21 Ben Greear wrote:
> I tested this code when it was combined into a single patch.
> There were still some issues, but I have no reason to believe
> this patch set caused them. This patch set significantly
> improved stability in my testing with 130+ STA interfaces.
one question: do you see similar issues with ath5k? i remember one bug is
filed with a rx poision issue.
thanks,
bruno
next prev parent reply other threads:[~2010-10-22 0:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 23:07 [PATCH 0/6] ath9k: fix RX poison issue Luis R. Rodriguez
2010-10-20 23:07 ` [PATCH 1/6] ath9k: add locking for stopping RX Luis R. Rodriguez
2010-10-20 23:07 ` [PATCH 2/6] ath9k: add locking for starting the PCU on RX Luis R. Rodriguez
2010-10-20 23:07 ` [PATCH 3/6] ath9k: rename rxflushlock to pcu_lock Luis R. Rodriguez
2010-10-21 6:03 ` Senthil Balasubramanian
2010-10-21 6:13 ` Luis R. Rodriguez
2010-10-21 7:05 ` Senthil Balasubramanian
2010-10-21 9:03 ` Luis R. Rodriguez
2010-10-20 23:07 ` [PATCH 4/6] ath9k: lock reset and PCU start/stopping Luis R. Rodriguez
2010-10-20 23:07 ` [PATCH 5/6] ath: add a ATH_DBG_WARN() Luis R. Rodriguez
2010-10-21 19:14 ` Luis R. Rodriguez
2010-10-20 23:07 ` [PATCH 6/6] ath9k: add a debug warning when we cannot stop RX Luis R. Rodriguez
2010-10-21 17:47 ` [PATCH 0/6] ath9k: fix RX poison issue Ben Greear
2010-10-22 0:30 ` Bruno Randolf [this message]
2010-10-22 0:32 ` Luis R. Rodriguez
2010-10-22 4:51 ` Ben Greear
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=201010220930.01071.br1@einfach.org \
--to=br1@einfach.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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).