From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: Fix to "All wake-up devices are disabled after suspend-to disk" isn't yet included in mainline
Date: Wed, 17 Oct 2007 06:27:26 +0200 [thread overview]
Message-ID: <200710170627.26136.maximlevitsky@gmail.com> (raw)
In-Reply-To: <20071016204802.9036ad96.akpm@linux-foundation.org>
On Wednesday 17 October 2007 05:48:02 Andrew Morton wrote:
> On Wed, 17 Oct 2007 04:39:30 +0200 Maxim Levitsky <maximlevitsky@gmail.com> wrote:
>
> > A while ago I asked on LKML about the problem of loosing all wake device capabilities, after a suspend to disk
> > (eg: I can't wake the system from keyboard if I suspend to disk and then to ram)
> >
> > I was provided with the patch that fixes this problem completely.
> > The merge window is open, but I still don't see it in the kernel.
> > Due to changes it doesn't anymore apply to latest git.
> >
> > Was it missed?
>
> No, it's in Len's git tree.
>
> Len's git-pull request from a few days ago didn't work, perhaps because I
> wanted to know if a recent -mm regression had been fixed and that hasn't
> been answered yet. I assume that Len is offline. Other acpi developers
> could presumably have answered that question but for some reason chose not to.
>
> I'm presently holding off 20-odd power management patches due to their
> dependency upon an acpi merge...
>
Thanks a lot.
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2007-10-17 4:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 2:39 Fix to "All wake-up devices are disabled after suspend-to disk" isn't yet included in mainline Maxim Levitsky
2007-10-17 3:48 ` Andrew Morton
2007-10-17 4:27 ` Maxim Levitsky [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=200710170627.26136.maximlevitsky@gmail.com \
--to=maximlevitsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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