From: Len Brown <lenb@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-acpi@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: git-acpi breaks resume-from-ram on the Vaio
Date: Tue, 18 Sep 2007 15:58:18 -0400 [thread overview]
Message-ID: <200709181558.19063.lenb@kernel.org> (raw)
In-Reply-To: <20070918100718.3d510356.akpm@linux-foundation.org>
On Tuesday 18 September 2007 13:07, Andrew Morton wrote:
> This breakage in git-acpi is new, I think. Four or five days ago, git-acpi
> _fixed_ suspend/resume on Linus's tree. Now it breaks it.
>
> But I don't think there have been changes in got-acpi since then, so
> perhaps the breakage is due to interaction with Thomas's recent merge.
hmmm, maybe.
Perhaps if you are including sony-laptop, you can try excluding it --
since these reverse engineered things are always fraught with peril....
I think the next thing to test is to revert cpuidle --
let me make sure that my cpuidle branch produces a patch
that will revert cleanly...
-Len
next prev parent reply other threads:[~2007-09-18 19:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 4:12 git-acpi breaks resume-from-ram on the Vaio Andrew Morton
2007-09-18 4:40 ` Andrew Morton
2007-09-18 11:54 ` Rafael J. Wysocki
2007-09-18 11:59 ` Rafael J. Wysocki
2007-09-19 7:27 ` Andrew Morton
2007-09-19 11:53 ` Rafael J. Wysocki
2007-09-19 14:47 ` Thomas Gleixner
2007-09-18 15:21 ` Len Brown
2007-09-18 15:47 ` Bissecting acpi merges (was Re: git-acpi breaks resume-from-ram on the Vaio) Henrique de Moraes Holschuh
2007-09-18 16:32 ` Len Brown
2007-09-18 17:07 ` git-acpi breaks resume-from-ram on the Vaio Andrew Morton
2007-09-18 18:04 ` Len Brown
2007-09-18 19:58 ` Len Brown [this message]
2007-09-18 20:25 ` Andrew Morton
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=200709181558.19063.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).