From: Len Brown <len.brown@intel.com>
To: sergiomb@netcabo.pt
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [ACPI] [PATCH] can we compile ACPI without define CONFIG_PM ?
Date: 07 May 2004 00:18:58 -0400 [thread overview]
Message-ID: <1083903538.2296.248.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615F9FD0@hdsmsx403.hd.intel.com>
Never occurred to me to build ACPI w/o CONFIG_PM...
There are #ifdef CONFIG_PM in the acpi code, so I guess this was on
purpose, but it makes ACPI a lot less interesting.
But I'm inclined to leave 2.4 alone except for real system failures.
The only clean-up I'm really interested in doing in 2.4 is when it makes
maintenance via backporting from 2.6 easier.
-Len
next parent reply other threads:[~2004-05-07 4:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F9FD0@hdsmsx403.hd.intel.com>
2004-05-07 4:18 ` Len Brown [this message]
2004-05-07 11:33 ` [ACPI] [PATCH] can we compile ACPI without define CONFIG_PM ? Sérgio Monteiro Basto
2004-05-07 14:52 ` Kevin P. Fleming
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=1083903538.2296.248.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sergiomb@netcabo.pt \
/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