From: "Tomas Winkler" <tomasw@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Carlos R. Mafra" <crmafra2@gmail.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Soeren Sonnenburg" <kernel@nn7.de>,
linux-kernel@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: Suspend to RAM regression in 2.6.28-rc2 (bisected)
Date: Tue, 28 Oct 2008 18:12:09 +0200 [thread overview]
Message-ID: <1ba2fa240810280912pea7284ejd6de5d04efbb974f@mail.gmail.com> (raw)
In-Reply-To: <200810281630.28389.rjw@sisk.pl>
On Tue, Oct 28, 2008 at 5:30 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Tuesday, 28 of October 2008, Tomas Winkler wrote:
>> h
>>
>> On Tue, Oct 28, 2008 at 12:50 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>> > On Monday, 27 of October 2008, Tomas Winkler wrote:
>> >> On Tue, Oct 28, 2008 at 12:28 AM, Carlos R. Mafra <crmafra2@gmail.com> wrote:
>> >> > On Mon 27.Oct'08 at 23:07:00 +0200, Tomas Winkler wrote:
>> >> >>[...]
>> >> >>
>> >> >> Can someone try this one (it might be space broken I've just pasted
>> >> >> that in) It's on top of 1d63e726408dfdb3e10ed8f00c383b30ebb333d3
>> >> >> (latest linux-2.6.git)
>> >> >
>> >> >
>> >> > Yes, this one also works for me (I applied it manually).
>> >> Good, this was actually part of some older and bigger patch I wasn't
>> >> aware it has this affect. It has some millage in iwl5000 branch.
>> >> RFKIll went through some changes in the mainline so it wasn't merged yet.
>> >
>> > Are you going to push this patch upstream now? It's quite important to get
>> > this resume regression fixed ASAP.
>>
>> Definitely I would post it to wireless and stable.
>
> Please send a CC to me too.
Hmm. It looks like I've misspelled your email when I've sent the patch.
Will send it again
Tomas
next prev parent reply other threads:[~2008-10-28 16:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 16:20 Carlos R. Mafra
2008-10-27 17:32 ` Rafael J. Wysocki
2008-10-27 18:07 ` Soeren Sonnenburg
2008-10-27 18:31 ` Johannes Berg
2008-10-27 18:44 ` Johannes Berg
2008-10-27 19:00 ` Carlos R. Mafra
2008-10-27 19:03 ` Johannes Berg
2008-10-27 19:11 ` Carlos R. Mafra
2008-10-27 19:13 ` Johannes Berg
2008-10-27 20:39 ` Carlos R. Mafra
2008-10-27 20:51 ` Rafael J. Wysocki
2008-10-27 20:52 ` Carlos R. Mafra
2008-10-27 21:07 ` Rafael J. Wysocki
2008-10-27 22:05 ` Carlos R. Mafra
2008-10-27 21:07 ` Tomas Winkler
2008-10-27 22:28 ` Carlos R. Mafra
2008-10-27 22:40 ` Tomas Winkler
2008-10-27 22:50 ` Rafael J. Wysocki
2008-10-27 23:12 ` Tomas Winkler
2008-10-27 23:23 ` Harvey Harrison
2008-10-28 15:30 ` Rafael J. Wysocki
2008-10-28 16:12 ` Tomas Winkler [this message]
2008-10-28 6:32 ` Christian Borntraeger
2008-10-27 19:06 ` Jens Axboe
2008-10-27 19:09 ` Johannes Berg
2008-10-27 19:13 ` Jens Axboe
2008-10-27 19:16 ` Johannes Berg
2008-10-27 19:20 ` Jens Axboe
2008-10-27 17:39 ` Rafael J. Wysocki
2008-10-27 17:57 ` Carlos R. Mafra
2008-10-27 18:00 ` John W. Linville
2008-10-27 18:16 ` Rafael J. Wysocki
2008-10-27 18:36 ` Carlos R. Mafra
2008-10-27 18:51 ` Carlos R. Mafra
2008-10-27 20:59 ` Christian Borntraeger
2008-10-27 21:06 ` Harvey Harrison
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=1ba2fa240810280912pea7284ejd6de5d04efbb974f@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=crmafra2@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rjw@sisk.pl \
/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
Powered by JetHome