From: "Jan Beulich" <jbeulich@suse.com>
To: <jinsong.liu@intel.com>, <konrad.wilk@oracle.com>
Cc: <keir.xen@gmail.com>, <len.brown@intel.com>,
<shaohua.li@intel.com>, <lenb@kernel.org>,
<xen-devel@lists.xensource.com>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] RFC: Prepare PAD for native and xen platform
Date: Thu, 23 Feb 2012 14:54:03 +0000 [thread overview]
Message-ID: <4F46530B020000780007F751@nat28.tlf.novell.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC82923350AD088@SHSMSX101.ccr.corp.intel.com>
>>> "Liu, Jinsong" <jinsong.liu@intel.com> 02/23/12 2:29 PM >>>
>--- a/drivers/acpi/Kconfig
>+++ b/drivers/acpi/Kconfig
>@@ -213,10 +213,11 @@ config ACPI_HOTPLUG_CPU
> default y
>
>config ACPI_PROCESSOR_AGGREGATOR
>- tristate "Processor Aggregator"
>+ bool "Processor Aggregator"
There must be ways to address whatever strange problem you see without
making this piece of code non-modular.
> depends on ACPI_PROCESSOR
> depends on EXPERIMENTAL
> depends on X86
>+ default n
This is pointless.
> help
> ACPI 4.0 defines processor Aggregator, which enables OS to perform
> specific processor configuration and control that applies to all
Jan
next prev parent reply other threads:[~2012-02-23 14:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 13:29 Liu, Jinsong
2012-02-23 14:54 ` Jan Beulich [this message]
2012-02-23 16:58 ` Liu, Jinsong
2012-02-24 8:37 ` Jan Beulich
2012-02-26 8:25 ` Liu, Jinsong
2012-02-26 17:34 ` Konrad Rzeszutek Wilk
2012-02-28 16:24 ` Liu, Jinsong
2012-02-29 8:01 ` [Xen-devel] " Liu, Jinsong
2012-03-26 7:21 ` Liu, Jinsong
2012-03-26 16:48 ` Konrad Rzeszutek Wilk
2012-03-29 7:04 ` Liu, Jinsong
2012-03-29 7:27 ` Liu, Jinsong
2012-03-29 18:08 ` Konrad Rzeszutek Wilk
2012-03-30 7:05 ` Liu, Jinsong
2012-03-30 21:13 ` Konrad Rzeszutek Wilk
2012-04-05 13:01 ` Liu, Jinsong
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=4F46530B020000780007F751@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=jinsong.liu@intel.com \
--cc=keir.xen@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=xen-devel@lists.xensource.com \
/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®