[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51A67DB4.9090404@sr71.net>
Date: Wed, 29 May 2013 15:14:12 -0700
From: Dave Hansen <dave@...1.net>
To: "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
CC: Toshi Kani <toshi.kani@...com>,
Dave Hansen <dave.hansen@...el.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>, linux-acpi@...r.kernel.org
Subject: Re: possible_cpus broken in linux-next
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@...el.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists