From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@users.sourceforge.net>,
Patrick Mochel <mochel@digitalimplant.org>
Cc: Andrew Morton <akpm@digeo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Suspend development list <swsusp-devel@lists.sourceforge.net>
Subject: Re: The verdict on the future of suspending to disk?
Date: Tue, 16 Mar 2004 12:37:17 +0100 [thread overview]
Message-ID: <20040316113717.GB2282@elf.ucw.cz> (raw)
In-Reply-To: <1079408330.3403.5.camel@calvin.wpcb.org.au>
Hi!
> Just wanting clarification; what are we thinking about the future of
> suspend implementations? Let me throw my current
> understanding/suggestion in for starters:
I'd like to know the results, too.
> - Drop PM_DISK?
I do not care which one is dropped as long as only one implementation
remains. Droping PM_DISK is indeed easiest as noone touched it for
half a year.
> - Apply patches making swsusp into suspend2, leaving out freezer changes
> until people are convinced the current solution is insufficient.
Could you prepare some "swsusp2 without freezer" patch, so that we can
see how it looks like?
> - Pavel keeps maintaining the end result? (I'm happy to maintain it if
> he wants; I'm assuming when I say this he'll still be dealing with S3
> and Patrick will be deal with PM support proper).
I do not think Patrick is going to maintain anything.
If you want to maintain it, you can have it. Big plus if you are able
to deal with Patrick.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-03-16 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 3:38 Nigel Cunningham
2004-03-16 8:05 ` [Swsusp-devel] " Karol Kozimor
2004-03-16 11:37 ` Pavel Machek [this message]
2004-03-16 12:15 ` Pavel Machek
2004-03-16 13:38 ` [Swsusp-devel] " Michael Frank
2004-03-16 15:10 ` Pavel Machek
2004-03-16 20:28 ` Nigel Cunningham
2004-03-16 20:13 ` Nigel Cunningham
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=20040316113717.GB2282@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=ncunningham@users.sourceforge.net \
--cc=swsusp-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®