From: Len Brown <lenb@kernel.org>
To: akpm@osdl.org
Cc: linux-acpi@vger.kernel.org
Subject: Re: [patch 07/19] acpi: don't select PM
Date: Wed, 20 Dec 2006 01:36:36 -0500 [thread overview]
Message-ID: <200612200136.36287.lenb@kernel.org> (raw)
In-Reply-To: <200612192056.kBJKuE4F010026@shell0.pdx.osdl.net>
On Tuesday 19 December 2006 15:56, akpm@osdl.org wrote:
> From: Andrew Morton <akpm@osdl.org>
>
> Make ACPI depend on PM rather than selecting it. Otherwise it's a nightmare
> working out why CONFIG_PM keeps getting set.
>
> (And why does ACPI require power management?)
I believe that this was to address a build failure
where ACPI and PM are entwined. It seemed to
make more sense to prohibit the uninteresting
configuration of (ACPI && !PM) rather than
to add a bunch of ifdefs.
I think the error in our ways was to use select
rather than depends -- not realizing the inherent
evils of select.
Applied.
thanks,
-Len
> Cc: "Brown, Len" <len.brown@intel.com>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
>
> drivers/acpi/Kconfig | 2 +-
> 1 files changed, 1 insertion(+), 1 deletion(-)
>
> diff -puN drivers/acpi/Kconfig~acpi-dont-select-pm drivers/acpi/Kconfig
> --- a/drivers/acpi/Kconfig~acpi-dont-select-pm
> +++ a/drivers/acpi/Kconfig
> @@ -11,7 +11,7 @@ config ACPI
> bool "ACPI Support"
> depends on IA64 || X86
> depends on PCI
> - select PM
> + depends on PM
> default y
> ---help---
> Advanced Configuration and Power Interface (ACPI) support for
> _
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2006-12-20 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 20:56 [patch 07/19] acpi: don't select PM akpm
2006-12-20 6:36 ` Len Brown [this message]
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=200612200136.36287.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=akpm@osdl.org \
--cc=linux-acpi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.