From: Pavel Machek <pavel@ucw.cz>
To: Michael Frank <mhf@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: Can swsusp 2.0 be merged into the 2.4 tree
Date: Fri, 12 Dec 2003 20:22:52 +0100 [thread overview]
Message-ID: <20031212192252.GA465@elf.ucw.cz> (raw)
In-Reply-To: <200312110537.17496.mhf@linuxmail.org>
Hi!
> swsusp is useful feature also for 2.4. Could this please be merged.
2.4 has no driver model => swsusp for 2.4 is a hack. Its nice and
working, but it is still a hack.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-12-12 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 21:39 RFC: Can swsusp 2.0 be merged into the 2.4 tree Michael Frank
2003-12-10 21:54 ` Mike Fedyk
2003-12-11 19:36 ` Michael Frank
2003-12-10 21:55 ` Matt H.
2003-12-12 19:22 ` Pavel Machek [this message]
2003-12-14 4:38 ` Nigel Cunningham
2003-12-14 11:03 ` Pavel Machek
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=20031212192252.GA465@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.org \
/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;
as well as URLs for NNTP newsgroup(s).