From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Dave Hansen <dave@sr71.net>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Toshi Kani <toshi.kani@hp.com>,
Dave Hansen <dave.hansen@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: possible_cpus broken in linux-next
Date: Thu, 30 May 2013 00:46:26 +0200 [thread overview]
Message-ID: <8225137.F3AGbHlx43@vostro.rjw.lan> (raw)
In-Reply-To: <51A67DB4.9090404@sr71.net>
On Wednesday, May 29, 2013 03:14:12 PM Dave Hansen wrote:
> On 05/29/2013 12:02 PM, Rafael J. Wysocki wrote:
> >>> diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
> >>> index 130ba0b..b9f0eec 100644
> >>> --- a/drivers/base/cpu.c
> >>> +++ b/drivers/base/cpu.c
> >>> @@ -281,6 +281,7 @@ int __cpuinit register_cpu(struct cpu *cpu, int num)
> >>> cpu->dev.bus = &cpu_subsys;
> >>> cpu->dev.release = cpu_device_release;
> >>> cpu->dev.offline_disabled = !cpu->hotpluggable;
> >>> + cpu->dev.offline = !cpu_online(num);
> >>> #ifdef CONFIG_ARCH_HAS_CPU_AUTOPROBE
> >>> cpu->dev.bus->uevent = arch_cpu_uevent;
> >>> #endif
>
> This gets things working for me again. Thanks for the quick response!
>
> Tested-by: Dave Hansen <dave.hansen@intel.com>
Applied.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-05-29 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 17:10 Dave Hansen
2013-05-29 18:35 ` Toshi Kani
2013-05-29 18:50 ` Toshi Kani
2013-05-29 19:02 ` Rafael J. Wysocki
2013-05-29 22:14 ` Dave Hansen
2013-05-29 22:46 ` Rafael J. Wysocki [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=8225137.F3AGbHlx43@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=dave.hansen@intel.com \
--cc=dave@sr71.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=toshi.kani@hp.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®