[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1185633870.2718.14.camel@localhost.localdomain>
Date: Sat, 28 Jul 2007 15:44:30 +0100
From: Sergio Monteiro Basto <sergio@...giomb.no-ip.org>
To: Stefan Richter <stefanr@...6.in-berlin.de>
Cc: Adrian Bunk <bunk@...sta.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>, Len Brown <lenb@...nel.org>,
david@...g.hm, Andrew Morton <akpm@...ux-foundation.org>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
Pavel Machek <pavel@....cz>
Subject: Re: [2.6 patch] let SUSPEND select HOTPLUG_CPU
On Sat, 2007-07-28 at 00:47 +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
> > The dependency of SUSPEND_SMP on HOTPLUG_CPU is quite unintuitive,
>
> It's not entirely unintuitive. That option's full name is "Support for
> suspend on SMP and hot-pluggable CPUs".
>
I have to give reason to Len Brown on limit the options else this is
much more difficult.
Make sense define SUSPEND_SMP without define HOTPLUG_CPU ?
or make sense define HOTPLUG_CPU without define SUSPEND_SMP ?
Even if both options could make sense, we have to have the code prepare
for it, which couldn't be prepared.
But it is more easier and more importante focus on major cases which is:
"I don't care" and force some configuration and everybody test the same
code. Else in ACPI we have many issues to resolve like with this define
and without other, which philosophically could be interesting but is not
the major case and don't let us focus on stability.
Thanks,
--
Sérgio M. B.
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (2192 bytes)
Powered by blists - more mailing lists