From: Andrew Morton <akpm@linux-foundation.org>
To: Len Brown <lenb@kernel.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 10:07:18 -0700 [thread overview]
Message-ID: <20070918100718.3d510356.akpm@linux-foundation.org> (raw)
In-Reply-To: <200709181121.41368.lenb@kernel.org>
On Tue, 18 Sep 2007 11:21:41 -0400 Len Brown <lenb@kernel.org> wrote:
> On Tuesday 18 September 2007 00:12, Andrew Morton wrote:
> >
> > It suspends OK, then during resume it gets partway through it, then everything
> > just stops.
>
> Hmmm, i thought your vaio resume problems were in linus' tree --
> did that go away -- or maybe it was in -mm and not in linus' tree all along?
It got fixed in Linus's tree by tglx's recent timers merge.
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.
> > Would prefer not to have to bisect this one - I've done enough bisecting this
> > week to last a lifetime, and bisecting git-acpi is painful due to build bustage
> > at various points (cpuidle).
>
> bisecting the acpi git three should work well, because it uses topic branches.
> This includes cpuidle. ie. unless the breakage is within the cpuidle branch itself,
> the whole cpuidle topic can be removed by skipping the single merge commit that
> pulls it in.
The breakage is within the cpuidle branch.
> If you like, I can build the topic branch heads and export plain patches
> for you to try. Also, I'll probably be re-writing the test branch history
> later today -- so let me know if you dig into it and i'll delay that until
> you're done.
I won't be doing anything here for a day or so.
I think what needs to happen is that the commits in the cpuidle code need
to be folded together. iirc the first couple of commits don't compile, and
the third one fixes them. Or something like that.
next prev parent reply other threads:[~2007-09-18 17:08 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 ` Andrew Morton [this message]
2007-09-18 18:04 ` git-acpi breaks resume-from-ram on the Vaio Len Brown
2007-09-18 19:58 ` Len Brown
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=20070918100718.3d510356.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=lenb@kernel.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).