Re: possible_cpus broken in linux-next

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx>

Applied.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux