From: Jason Uhlenkott <jasonuhl-sJ/iWh9BUns@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: 2.6.12-rc1-mm3
Date: Fri, 25 Mar 2005 21:52:55 -0800 [thread overview]
Message-ID: <20050326055255.GA210003@dragonfly.engr.sgi.com> (raw)
In-Reply-To: <1111810359.19919.113.camel@d845pe>
On Fri, Mar 25, 2005 at 11:12:39PM -0500, Len Brown wrote:
> I realize now I didn't answer your original question.
> The reason ACPI now depends on PM is that
> it makes it easier for us to do a more orderly shutdown --
> acpi registers as a device so it can do some stuff
> upon the PM device shutdowns -- before interrupts are disabled.
>
> I think with all the twisty turney passages
> related to the suspend states, poweroff, sys-req, and now kexec,
> that it is best if we can keep the code paths as
> common as possible or some of them will never get the
> testing needed to prevent them from getting broken.
>
> Also, it is now common practice to include PM && ACPI together
> in the x86 world. Though technically one could have
> ACPI w/o PM and you'd have lost only ACPI_SLEEP, virtually
> nobody seems to use/depend-on that combination.
OK, that makes sense. I see now that Jesse has already sent a patch
to allow CONFIG_PM on sn2, so we'll be fine as soon as that gets
merged.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-03-26 5:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050325002154.335c6b0b.akpm@osdl.org>
2005-03-26 1:43 ` 2.6.12-rc1-mm3 Jason Uhlenkott
[not found] ` <20050326014327.GB207782-MxuHJOjpcnauM61iycY1Zzbuus4N2nEH@public.gmane.org>
2005-03-26 1:56 ` 2.6.12-rc1-mm3 Len Brown
2005-03-26 2:02 ` [ACPI] " Jason Uhlenkott
[not found] ` <20050326020212.GC207782-MxuHJOjpcnauM61iycY1Zzbuus4N2nEH@public.gmane.org>
2005-03-26 2:24 ` Len Brown
2005-03-26 2:57 ` [ACPI] " Jason Uhlenkott
[not found] ` <20050326025704.GE207782-MxuHJOjpcnauM61iycY1Zzbuus4N2nEH@public.gmane.org>
2005-03-26 3:40 ` Jesse Barnes
2005-03-26 4:12 ` [ACPI] " Len Brown
2005-03-26 5:52 ` Jason Uhlenkott [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=20050326055255.GA210003@dragonfly.engr.sgi.com \
--to=jasonuhl-sj/iwh9buns@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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