From: Pavel Machek <pavel@ucw.cz>
To: Harald Arnesen <harald@skogtun.org>
Cc: Nigel Cunningham <ncunningham@cyclades.com>,
Mark Lord <lkml@rtr.ca>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: regular swsusp flamewar
Date: Tue, 28 Mar 2006 11:13:44 +0200 [thread overview]
Message-ID: <20060328091344.GC2874@elf.ucw.cz> (raw)
In-Reply-To: <87mzfb9xnd.fsf@basilikum.skogtun.org>
On Út 28-03-06 03:16:22, Harald Arnesen wrote:
> The main point for me is that suspend2 works, while mainline supspend
> does not ("works": it takes less time to suspend/resume than to
> shutdown/reboot).
>
> I haven't tried uswsusp yet. Why try another out-of-kernel suspend when
> suspend2 works perfectly?
uswsusp is not out-of-tree any more (but you'll need recent tree from
git). You should try in-kernel options before patching your kernel,
I'd say. Userland tools are at suspend.sf.net.
Pavel
--
Picture of sleeping (Linux) penguin wanted...
next prev parent reply other threads:[~2006-03-28 10:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200603231702.k2NH2OSC006774@hera.kernel.org>
2006-03-23 21:13 ` [PATCH] swsusp: separate swap-writing/reading code Nigel Cunningham
2006-03-23 21:53 ` Rafael J. Wysocki
2006-03-23 22:48 ` Mark Lord
2006-03-23 23:39 ` Rafael J. Wysocki
2006-03-27 10:26 ` Pavel Machek
2006-03-27 10:43 ` Nigel Cunningham
2006-03-27 23:15 ` regular swsusp flamewar [was Re: [PATCH] swsusp: separate swap-writing/reading code] Pavel Machek
2006-03-27 23:36 ` Nigel Cunningham
2006-03-28 1:18 ` regular swsusp flamewar Harald Arnesen
2006-03-28 9:15 ` regular swsusp flamewar [was Re: [PATCH] swsusp: separate swap-writing/reading code] Pavel Machek
2006-03-28 9:16 ` Pavel Machek
2006-03-28 10:28 ` Nigel Cunningham
2006-03-28 1:16 ` regular swsusp flamewar Harald Arnesen
2006-03-28 9:13 ` Pavel Machek [this message]
2006-03-23 23:58 ` [PATCH] swsusp: separate swap-writing/reading code Andrew Morton
2006-03-24 0:32 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060328091344.GC2874@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=harald@skogtun.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=ncunningham@cyclades.com \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox