From: Jeff Garzik <jgarzik@pobox.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Eric Altendorf <EricAltendorf@orst.edu>,
Jochen Hein <jochen@jochen.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
andrew.grover@intel.com
Subject: Re: [2.5.50, ACPI] link error
Date: Thu, 05 Dec 2002 17:27:26 -0500 [thread overview]
Message-ID: <3DEFD2CE.4070805@pobox.com> (raw)
In-Reply-To: <20021205222431.GB7396@atrey.karlin.mff.cuni.cz>
Pavel Machek wrote:
> Yes, there are about 10 patches to fix it floating around... I just
> hope linus takes one of them. (Fix is make ACPI_SLEEP depend on
> swsusp).
I haven't seen the patch, but does it make sense for hardware suspend to
depend on software suspend?
IMO there should be a common core (CONFIG_SUSPEND?), not force ACPI to
depend on swsusp. That way you get the _least_ common denominator, not
the union of two sets.
Jeff
next prev parent reply other threads:[~2002-12-05 22:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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-06 18:57 ` [ACPI] " Ducrot Bruno
2002-12-06 23:05 ` Ducrot Bruno
2002-12-08 19:49 ` Pavel Machek
2002-12-08 20:46 ` Constantinos Antoniou
2002-12-09 10:40 ` Ducrot Bruno
2002-12-09 10:28 ` Ducrot Bruno
2002-12-09 11:01 ` Pavel Machek
2002-12-09 17:42 ` Ducrot Bruno
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
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
[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
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=3DEFD2CE.4070805@pobox.com \
--to=jgarzik@pobox.com \
--cc=EricAltendorf@orst.edu \
--cc=andrew.grover@intel.com \
--cc=jochen@jochen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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
Powered by JetHome