From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacek Kawa Subject: Re: [RFC] userland swsusp Date: Thu, 17 Nov 2005 21:15:09 +0100 Message-ID: <20051117201509.GA25250@finwe.eu.org> References: <20051116191051.GG2193@spitz.ucw.cz> <20051117165437.GA10402@dspnet.fr.eu.org> <20051117164451.GA27178@kroah.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6246456953180195==" Return-path: In-Reply-To: <20051117164451.GA27178@kroah.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: Greg KH Cc: Linux-pm mailing list , kernel list List-Id: linux-pm@vger.kernel.org --===============6246456953180195== Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greg KH wrote: > > > What unstable implementation? swsusp had very little regressions over past > > > year or so. Drivers were different story, but nothing changes w.r.t. drivers. > > Do you mean swsusp is actually supposed to work? Suspend-to-ram, > > suspend-to-disk or both? > Both. -to-ram depends on your video chip, but to-disk should work just > fine. If not, please report bugs. Thanks, I've just realized, that I probably forgot to CC anyone last time... :) So, may I kindly ask to look on: http://www.ussg.iu.edu/hypermail/linux/kernel/0511.1/1863.html ? Thanks! -- Jacek Kawa --===============6246456953180195== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============6246456953180195==--