On Thu, 30 Aug 2007, Rafael J. Wysocki wrote:
> On Thursday, 30 August 2007 14:40, Hugh Dickins wrote:
> >
> > I wonder what config options this might have forced in the past.
>
> Probably CONFIG_SUSPEND, which was a new option, defaulted to 'y' and
> selected CONFIG_HOTPLUG_CPU indirectly, because CONFIG_SMP was set.
In fact no: although CONFIG_SUSPEND and CONFIG_HIBERNATION were certainly
involved in the logic which arrived at missetting CONFIG_HOTPLUG_CPU,
they were correctly prompted for themselves.
Hugh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
