All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/6] ath9k: fix RX poison issue
Date: Thu, 21 Oct 2010 10:47:21 -0700	[thread overview]
Message-ID: <4CC07CA9.4040808@candelatech.com> (raw)
In-Reply-To: <1287616028-12547-1-git-send-email-lrodriguez@atheros.com>

On 10/20/2010 04:07 PM, Luis R. Rodriguez wrote:
> This series addresses the RX poison issue reported by Ben.
> I've split the patches up into as many atomic pieces to make
> it easier for review and understanding. Some are stable, the
> last few patches are for debugging.
>
> Luis R. Rodriguez (6):
>    ath9k: add locking for stopping RX
>    ath9k: add locking for starting the PCU on RX
>    ath9k: rename rxflushlock to pcu_lock
>    ath9k: lock reset and PCU start/stopping
>    ath: add a ATH_DBG_WARN()
>    ath9k: add a debug warning when we cannot stop RX
>
>   drivers/net/wireless/ath/ath9k/ath9k.h |    2 +-
>   drivers/net/wireless/ath/ath9k/main.c  |   31 +++++++++++++++++++++++++++++--
>   drivers/net/wireless/ath/ath9k/recv.c  |   17 +++++++++--------
>   drivers/net/wireless/ath/debug.h       |    2 ++
>   4 files changed, 41 insertions(+), 11 deletions(-)

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.

So:

Tested-by: Ben Greear <greearb@candelatech.com>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  parent reply	other threads:[~2010-10-21 17:47 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 ` Ben Greear [this message]
2010-10-22  0:30   ` [PATCH 0/6] ath9k: fix RX poison issue Bruno Randolf
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=4CC07CA9.4040808@candelatech.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.