From: Jochen Hein <jochen-AVN6mSxK9lsdnm+yROfE0A@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: wrong documentation for /proc/acpi/sleep?
Date: Mon, 19 Sep 2005 08:50:17 +0200 [thread overview]
Message-ID: <871x3l4kly.fsf@echidna.jochen.org> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3004A13DD5-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org> (Len Brown's message of "Sun, 18 Sep 2005 23:08:05 -0400")
"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> writes:
> Seems it is pretty obscure to enable SMP SLEEP in Kconfig.
Yes, it is ;-)
>>So, wouldn't it be far easier for a user to get all the needed symbols
>>selected, instead of hunting dependencies in Kconfig? For me it
>>doesn't matter *what* options I need for ACPI_SLEEP. I just want it
>>enabled.
On further thinking, why does Suspend-to-RAM need HOTPLUG_CPU, but
Suspend-to-Disk works without? Might help in finding a better
solution.
Jochen
--
#include <~/.signature>: permission denied
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
next prev parent reply other threads:[~2005-09-19 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 3:08 wrong documentation for /proc/acpi/sleep? Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B3004A13DD5-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-09-19 6:50 ` Jochen Hein [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-19 8:29 Li, Shaohua
[not found] <87mzme3xv8.fsf@echidna.jochen.org>
[not found] ` <87mzme3xv8.fsf-p0EyZM+cOqMBU3qZLEr2Wx2eb7JE58TQ@public.gmane.org>
2005-09-15 21:42 ` Len Brown
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=871x3l4kly.fsf@echidna.jochen.org \
--to=jochen-avn6msxk9lsdnm+yrofe0a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@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