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 00/10] ath9k / mac80211: power save fixes
Date: Tue, 14 Sep 2010 08:53:09 -0700 [thread overview]
Message-ID: <4C8F9A65.3040204@candelatech.com> (raw)
In-Reply-To: <AANLkTikazs3A+=BXVm9+VZaOsRD2YFSkRSDJKQ4qGBfB@mail.gmail.com>
On 09/14/2010 08:07 AM, Luis R. Rodriguez wrote:
> On Mon, Sep 13, 2010 at 10:30 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
>> Here are a bundle of joy of fixes for power save. Some of
>> these are regressions, which sucks ass to find out about them
>> so late. We *really* need a regression testbed for mac80211 and
>> ath9k. Some stable fixes trickle down to 2.6.32 even.
We're working on supporting ath9k for the virtual interfaces
in our system, and we do our own regression testing.
Aside from normal traffic passing, do you have any test
cases you'd like to see run?
> The all in one git am'able file can be downloaded here:
>
> http://bombadil.infradead.org/~mcgrof/patches/ath9k/2010/09/all-ps-fixes-09-14-v1.patch
Is there any way to get automated emails for commits going into wireless-testing?
If these go in soon, I'd rather not deal with merging them into my own repo,
but if it's going to take a while, it might be worth the effort.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-09-14 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 5:30 [PATCH 00/10] ath9k / mac80211: power save fixes Luis R. Rodriguez
2010-09-14 15:07 ` Luis R. Rodriguez
2010-09-14 15:53 ` Ben Greear [this message]
2010-09-14 16:09 ` Luis R. Rodriguez
2010-09-14 16:25 ` Ben Greear
2010-09-14 16:34 ` Johannes Berg
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=4C8F9A65.3040204@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.