From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
konrad@kernel.org, xen-devel@lists.xensource.com
Subject: Re: [PATCH] fixes to ACPI subsystem which assumes cpuidle is always enabled.
Date: Fri, 18 Jan 2013 10:12:19 -0500 [thread overview]
Message-ID: <20130118151219.GI9214@phenom.dumpdata.com> (raw)
In-Reply-To: <1449747.HgoeXlbhzH@vostro.rjw.lan>
On Wed, Jan 16, 2013 at 11:49:00PM +0100, Rafael J. Wysocki wrote:
> On Tuesday, January 15, 2013 05:23:22 PM Konrad Rzeszutek Wilk wrote:
> > Attached are two patches to the ACPI subsystem and the cpuidle drivers.
> >
> > The fixes are to deal with the case when cpuidle_disabled returns true
> > and we try to hotplug CPUs on/off.
> >
> > drivers/acpi/processor_idle.c | 3 +++
> > drivers/idle/intel_idle.c | 3 +--
> > 2 files changed, 4 insertions(+), 2 deletions(-)
>
> Both patches applied.
Thanks!
>
> Thanks,
> Rafael
>
>
> --
> I speak only for myself.
> Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-01-18 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 22:23 [PATCH] fixes to ACPI subsystem which assumes cpuidle is always enabled Konrad Rzeszutek Wilk
2013-01-15 22:23 ` [PATCH 1/2] ACPI: intel-idle: Don't register CPU notifier if we are not running Konrad Rzeszutek Wilk
2013-01-15 22:33 ` Rafael J. Wysocki
2013-01-15 22:30 ` Konrad Rzeszutek Wilk
2013-01-16 8:10 ` Srivatsa S. Bhat
2013-01-15 22:23 ` [PATCH 2/2] ACPI / cpuidle: Fix NULL pointer issues when cpuidle is disabled Konrad Rzeszutek Wilk
2013-01-15 22:45 ` Rafael J. Wysocki
2013-01-16 4:42 ` Konrad Rzeszutek Wilk
2013-01-16 22:49 ` [PATCH] fixes to ACPI subsystem which assumes cpuidle is always enabled Rafael J. Wysocki
2013-01-18 15:12 ` Konrad Rzeszutek Wilk [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=20130118151219.GI9214@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=konrad@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--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