linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Gertjan van Wingerde <gwingerde@gmail.com>,
	users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/4] rt2x00: Powersave fixes.
Date: Tue, 6 Apr 2010 23:26:48 +0200	[thread overview]
Message-ID: <201004062326.48463.IvDoorn@gmail.com> (raw)
In-Reply-To: <4BBB90F6.8060406@gmail.com>

On Tuesday 06 April 2010, Gertjan van Wingerde wrote:
> On 04/06/10 21:34, John W. Linville wrote:
> > On Tue, Mar 30, 2010 at 11:50:22PM +0200, Gertjan van Wingerde wrote:
> >> The following 4 patches fix powersave behavior of rt2x00.
> >> The first patch fixes the rt2500usb powersave issues found lately.
> >> The second on enables powersave for rt2500usb again, now it is fixed.
> >> The third and fourth are ongoing work to bring the other PCI drivers
> >> in a better shape.
> >>
> >> All patches are against wireless-2.6.
> >>
> >> The patch series is also available via:
> >>
> >> 	git://git.gwingerde.nl/rt2x00-2.6.git
> >>
> >> Gertjan van Wingerde (4):
> >>   rt2x00: Disable auto wakeup before waking up device.
> >>   rt2x00: Enable powersaving by default again on rt2500usb.
> >>   rt2x00: Add wakeup interrupt handler to rt61pci.
> >>   rt2x00: Add wakeup interrupt handler to rt2800pci.
> > 
> > I don't have any objection to these patches, but they don't
> > seem appropriate for 2.6.34 to me.  As such, basing them on
> > wireless-next-2.6 seems more appropriate.
> > 
> > Any objection to me applying them for 2.6.35?
> > 
> 
> You're the boss ;-)
> 
> No, no objections from my side. We already disabled powersaving in 2.6.34,
> so we should be covered for that release.
> 
> Note that patch 2 then won't apply to wireless-next-2.6, as the patch
> that disables powersaving is only in wireless-2.6.
> 
> How do you want to handle applying patch 2 from the series; how do we
> synchronize?

John, not sure how important you consider it, but please note that the first 2 patches would fix:
https://bugzilla.kernel.org/show_bug.cgi?id=15699

Ivo

      parent reply	other threads:[~2010-04-06 21:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 21:50 [PATCH 0/4] rt2x00: Powersave fixes Gertjan van Wingerde
2010-03-30 21:50 ` [PATCH 1/4] rt2x00: Disable auto wakeup before waking up device Gertjan van Wingerde
2010-03-30 21:50 ` [PATCH 2/4] rt2x00: Enable powersaving by default again on rt2500usb Gertjan van Wingerde
2010-03-31 22:29   ` Adam Baker
2010-03-31 22:34     ` Gertjan van Wingerde
2010-03-30 21:50 ` [PATCH 3/4] rt2x00: Add wakeup interrupt handler to rt61pci Gertjan van Wingerde
2010-03-30 21:50 ` [PATCH 4/4] rt2x00: Add wakeup interrupt handler to rt2800pci Gertjan van Wingerde
2010-04-06 19:34 ` [PATCH 0/4] rt2x00: Powersave fixes John W. Linville
2010-04-06 19:52   ` Gertjan van Wingerde
2010-04-06 21:18     ` John W. Linville
2010-04-06 21:26     ` Ivo van Doorn [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=201004062326.48463.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=gwingerde@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=users@rt2x00.serialmonkey.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).