From: Roman Zippel <zippel@linux-m68k.org>
To: Shawn Starr <shawn.starr@datawire.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.50, ACPI] link error
Date: Thu, 5 Dec 2002 17:47:42 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0212051729120.2113-100000@serv> (raw)
In-Reply-To: <200212051057.14882.shawn.starr@datawire.net>
Hi,
On Thu, 5 Dec 2002, Shawn Starr wrote:
> SLEEP SUSPEND SLEEP visible SUSPEND visible
> n n y n
> y n y y
> y y y y
>
> We really do need recursive support though. A user should not be able to
> select SOFTWARE_SUSPEND without SLEEP selected.
So just let SOFTWARE_SUSPEND depend on ACPI_SLEEP, if ACPI_SLEEP is
independent it doesn't has to depend on SUSPEND.
Another possibility is that you might want to restore the old behaviour,
that SOFTWARE_SUSPEND is always visible and forces ACPI_SLEEP to y if
needed, but then you have to explicitly disable the user prompt and
SOFTWARE_SUSPEND must not depend on ACPI_SLEEP:
config ACPI_SLEEP
bool "Sleep States" if !SOFTWARE_SUSPEND
default SOFTWARE_SUSPEND
config SOFTWARE_SUSPEND
bool "Software Suspend (EXPERIMENTAL)"
depends on EXPERIMENTAL && PM
bye, Roman
PS: Could you check your mailer why your mails don't reach lkml?
next prev parent reply other threads:[~2002-12-05 16:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200212042312.gB4NC8UJ021406@BlackBerry.NET>
2002-12-04 23:37 ` Roman Zippel
[not found] ` <200212051057.14882.shawn.starr@datawire.net>
2002-12-05 16:47 ` Roman Zippel [this message]
2002-12-04 21:05 Shawn Starr
2002-12-04 21:26 ` Roman Zippel
[not found] ` <200212041630.40446.shawn.starr@datawire.net>
2002-12-04 21:44 ` Roman Zippel
[not found] ` <200212041653.04475.shawn.starr@datawire.net>
[not found] ` <200212041720.14647.shawn.starr@datawire.net>
2002-12-04 22:40 ` Roman Zippel
2002-12-06 8:17 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-12-02 20:24 Jochen Hein
2002-12-03 18:07 ` Eric Altendorf
2002-12-03 18:35 ` Jochen Hein
2002-12-03 20:47 ` Eric Altendorf
2002-12-05 17:31 ` Pavel Machek
2002-12-05 22:21 ` Jeff Garzik
2002-12-05 22:24 ` Pavel Machek
2002-12-05 22:27 ` Jeff Garzik
2002-12-05 22:33 ` Pavel Machek
2002-12-05 22:38 ` Jeff Garzik
2002-12-05 22:40 ` Pavel Machek
2002-12-05 22:43 ` Patrick Mochel
2002-12-06 0:06 ` Pavel Machek
2002-12-06 0:05 ` Patrick Mochel
2002-12-06 0:31 ` Pavel Machek
2002-12-06 0:36 ` Jeff Garzik
2002-12-07 14:02 ` David Ford
2002-12-07 5:50 ` Eric Altendorf
2002-12-09 7:29 ` Pavel Machek
2002-12-16 3:40 ` Eric Altendorf
2002-12-16 11:16 ` Pavel Machek
2002-12-04 11:41 ` Pavel Machek
2002-12-04 13:50 ` Adrian Bunk
2002-12-04 19:16 ` Jochen Hein
2002-12-04 20:29 ` Roman Zippel
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=Pine.LNX.4.44.0212051729120.2113-100000@serv \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.starr@datawire.net \
/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
all inboxes | Powered by JetHome®