From: Shawn Starr <shawn.starr@datawire.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.5.50, ACPI] link error
Date: Wed, 4 Dec 2002 16:05:11 -0500 [thread overview]
Message-ID: <200212041605.11935.shawn.starr@datawire.net> (raw)
Thats what I thought until Pavel told me SOFTWARE_SUSPEND requires ACPI_SLEEP
and ACPI_SLEEP should not be unchecked if SOFTWARE_SUSPEND is disabled.
My patch was only to fix a link error in 2.5.49/50. A better solution is
needed :-)
Shawn.
>List: linux-kernel
>Subject: Re: [2.5.50, ACPI] link error
From: Roman Zippel <zippel@linux-m68k.org>
>Date: 2002-12-04 20:29:08
>[Download message RAW]
>
>Hi,
>
>On Wed, 4 Dec 2002, Adrian Bunk wrote:
>
> In drivers/acpi/Config.in in 2.5.44:
>
> <-- snip -->
>
> ...
> if [ "$CONFIG_ACPI_HT_ONLY" != "y" ]; then
> bool ' Sleep States' CONFIG_ACPI_SLEEP
> ...
> define_bool CONFIG_ACPI_SLEEP $CONFIG_SOFTWARE_SUSPEND
> ...
> fi
> ...
>
> <-- snip -->
>
>
> This double definition was at least confusing, a simple
>
> dep_bool ' Sleep States' CONFIG_ACPI_SLEEP $CONFIG_SOFTWARE_SUSPEND
>
> would have expressed it better.
>It's not really the same and the first probably heavily confuses xconfig.
>If CONFIG_SOFTWARE_SUSPEND can do without CONFIG_ACPI_SLEEP, the second
>version should work fine.
> config ACPI_SLEEP
> bool "Sleep States"
> - depends on X86 && ACPI && !ACPI_HT_ONLY
> + depends on X86 && ACPI && !ACPI_HT_ONLY && SOFTWARE_SUSPEND
> default SOFTWARE_SUSPEND
> ---help---
> This option adds support for ACPI suspend states.
>The default is probably not needed anymore.
--
Shawn Starr
UNIX Systems Administrator, Operations
Datawire Communication Networks Inc.
10 Carlson Court, Suite 300
Toronto, ON, M9W 6L2
T: 416-213-2001 ext 179 F: 416-213-2008
shawn.starr@datawire.net
"The power to Transact" - http://www.datawire.net
next reply other threads:[~2002-12-04 20:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 21:05 Shawn Starr [this message]
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
[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
-- 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=200212041605.11935.shawn.starr@datawire.net \
--to=shawn.starr@datawire.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®