All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linux-wireless@vger.kernel.org, kyungwan.nam@atheros.com
Subject: Re: [RFT 0/3] ath9k: more PCU locking enhancements
Date: Tue, 26 Oct 2010 09:33:09 -0700	[thread overview]
Message-ID: <4CC702C5.6090907@candelatech.com> (raw)
In-Reply-To: <1288082441-4882-1-git-send-email-lrodriguez@atheros.com>

On 10/26/2010 01:40 AM, Luis R. Rodriguez wrote:
> Here is some more PCU locking enhancements I tested today
> while trying to resolve the WARN() that happens when we
> try to stop RX DMA and fail. While working on that I figured
> I'd work on the TX DMA stuff too, here's a shot at it. I
> can no longer get TX / RX DMA rants, please test and let
> me know if you do. I only tried some basic testing like
> rmmoding while scannign, which typicallly produced some
> errors. Now I don't get squat.
>
> Ben if you can test wit your super proprietary application
> that'd be great.

I'll make every effort, we should have some testing results later
today.

Thanks,
Ben

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


  parent reply	other threads:[~2010-10-26 16:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  8:40 [RFT 0/3] ath9k: more PCU locking enhancements Luis R. Rodriguez
2010-10-26  8:40 ` [RFT 1/3] ath9k: simplify hw reset locking Luis R. Rodriguez
2010-10-26  8:40 ` [RFT 2/3] ath9k: move the PCU lock to the sc structure Luis R. Rodriguez
2010-10-26  8:40 ` [RFT 3/3] ath9k: content DMA start / stop through the PCU lock Luis R. Rodriguez
2010-10-26 16:33 ` Ben Greear [this message]
2010-10-26 21:59 ` [RFT 0/3] ath9k: more PCU locking enhancements Ben Greear
2010-10-26 22:03   ` Luis R. Rodriguez
2010-10-26 22:11     ` Ben Greear
2010-10-26 22:17       ` Luis R. Rodriguez
2010-10-27 16:17         ` Ben Greear
2010-10-27 16:26           ` Luis R. Rodriguez
2010-10-27 16:38             ` Ben Greear
2010-10-27 18:55               ` Luis R. Rodriguez

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=4CC702C5.6090907@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=kyungwan.nam@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --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.