[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200707291220.14880.rjw@sisk.pl>
Date: Sun, 29 Jul 2007 12:20:13 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: 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>, Adrian Bunk <bunk@...sta.de>,
Stefan Richter <stefanr@...6.in-berlin.de>,
Nigel Cunningham <nigel@...el.suspend2.net>,
pm list <linux-pm@...ts.linux-foundation.org>
Subject: [PATCH 0/2] Introduce CONFIG_HIBERNATION and CONFIG_SUSPEND (was: CONFIG_SUSPEND?)
On Saturday, 28 July 2007 20:31, Linus Torvalds wrote:
>
> On Sat, 28 Jul 2007, Rafael J. Wysocki wrote:
> >
> > OK, I'll prepare a patch to introduce CONFIG_SUSPEND, but that will require
> > quite a bit of (compilation) testing on different architectures.
>
> Sure. I'm not too worried, the fallout should be of the trivial kind.
>
> Also, mind basing it on the (independent) cleanups that Adrian already
> sent out. This is all intertwined..
OK, it took more time than I had hoped, but I wanted CONFIG_HIBERNATION and
CONFIG_SUSPEND to be really independent of each other.
The two patches in the next messages implement the idea:
* replace CONFIG_SOFTWARE_SUSPEND with CONFIG_HIBERNATION
* introduce CONFIG_SUSPEND that selects CONFIG_HOTPLUG_CPU, if necessary,
and make it possible to choose suspend and hibernation independently of each
other.
Greetings,
Rafael
-
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