[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1186392591.28655.35.camel@johannes.berg>
Date: Mon, 06 Aug 2007 11:29:51 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Pavel Machek <pavel@....cz>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Andi Kleen <ak@...e.de>,
LKML <linux-kernel@...r.kernel.org>,
Adrian Bunk <bunk@...sta.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
pm list <linux-pm@...ts.linux-foundation.org>,
Russell King <rmk@....linux.org.uk>
Subject: Re: [linux-pm] Re: [Resend][PATCH] PM: Fix dependencies of
CONFIG_SUSPEND and CONFIG_HIBERNATION (updated)
On Mon, 2007-08-06 at 11:07 +0200, Pavel Machek wrote:
> Hi!
>
> > +config SUSPEND_UP_POSSIBLE
> > + bool
> > + depends on (X86 && !X86_VOYAGER) || (PPC32 && PPC_MPC52xx) \
> > + || (PPC64 && (PPC_PSERIES || PPC_PMAC)) || ARM || BLACKFIN \
> > + || MIPS || SUPERH || FRV
> > + depends on !SMP
> > + default y
>
> I guess I'd rather left SUSPEND_UP_POSSIBLE to allways y (as it always
> was), and let architectures that can't handle it not return "mem"
> from list of valid states...
Yeah, that's the utterly broken interface we used to have. Until I fixed
it to have no valid states until architectures implement suspend_ops.
Still, I disagree, why bother with compiling code that can't ever be
used?
johannes
Download attachment "signature.asc" of type "application/pgp-signature" (191 bytes)
Powered by blists - more mailing lists