From: Nigel Cunningham <ncunningham@linuxmail.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>,
hugang@soulinfo.com
Subject: Re: swsusp bigdiff [was Re: [PATCH] Software Suspend split to two stage V2.]
Date: Tue, 23 Nov 2004 08:50:49 +1100 [thread overview]
Message-ID: <1101160249.7962.52.camel@desktop.cunninghams> (raw)
In-Reply-To: <200411221254.40732.rjw@sisk.pl>
Hi.
You guys are slowly developing swsusp into suspend2 :>. Just in case
you're wondering, I haven't given up on merging; I've just been seeking
to get it as bug free as possible, do clean ups and documentation and so
on before getting stuck in to submitting it.
Regards,
Nigel
On Mon, 2004-11-22 at 22:54, Rafael J. Wysocki wrote:
> On Monday 22 of November 2004 12:02, Pavel Machek wrote:
> > Hi!
> >
> > > > Yes, I'd like to get rid of "too many continuous pages" problem
> > > > before. Small problem is that it needs to update x86-64 too, but I
> > > I have not x86-64, so I have no chance to do it.
> >
> > I have access to x86-64, so I can do it...
>
> Please, let me know when you have it done. I'd like to test ... ;-)
>
> RJW
--
Nigel Cunningham
Pastoral Worker
Christian Reformed Church of Tuggeranong
PO Box 1004, Tuggeranong, ACT 2901
You see, at just the right time, when we were still powerless, Christ
died for the ungodly. -- Romans 5:6
next prev parent reply other threads:[~2004-11-22 22:03 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 19:40 [PATCH] Software Suspend split to two stage V2 hugang
2004-11-20 0:15 ` Pavel Machek
2004-11-20 0:30 ` swsusp bigdiff [was Re: [PATCH] Software Suspend split to two stage V2.] Pavel Machek
2004-11-20 3:03 ` hugang
2004-11-20 10:15 ` Pavel Machek
2004-11-20 8:12 ` hugang
2004-11-20 21:22 ` Pavel Machek
2004-11-20 21:41 ` Pavel Machek
2004-11-20 22:35 ` Pavel Machek
2004-11-20 22:49 ` Pavel Machek
2004-11-21 7:48 ` hugang
2004-11-22 7:22 ` hugang
2004-11-22 10:26 ` Pavel Machek
2004-11-22 10:32 ` hugang
2004-11-22 11:02 ` Pavel Machek
2004-11-22 11:54 ` Rafael J. Wysocki
2004-11-22 21:50 ` Nigel Cunningham [this message]
2004-11-23 21:54 ` Pavel Machek
2004-11-23 21:57 ` Nigel Cunningham
2004-11-24 8:03 ` [PATH] 11-24 swsusp update 2/3 hugang
2004-11-24 8:04 ` [PATH] 11-24 swsusp update 3/3 hugang
2004-11-24 9:13 ` hugang
2004-11-24 14:05 ` Colin Leroy
2004-11-22 16:58 ` [PATH] swsusp update 1/3 hugang
2004-11-23 22:14 ` Pavel Machek
2004-11-24 8:02 ` [PATH] 11-24 " hugang
2004-11-24 10:56 ` Pavel Machek
2004-11-24 11:28 ` [PATH] " Pavel Machek
2004-11-24 18:30 ` hugang
2004-12-20 21:45 ` Nishanth Aravamudan
2004-12-20 22:41 ` Pavel Machek
2004-11-22 16:58 ` [PATH] swsusp update 2/3 hugang
2004-11-23 22:23 ` Pavel Machek
2004-11-22 16:58 ` [PATH] swsusp update 3/3 hugang
2004-11-23 22:29 ` Pavel Machek
2004-11-24 10:21 ` Guido Guenther
2004-11-20 9:27 ` swsusp bigdiff [was Re: [PATCH] Software Suspend split to two stage V2.] hugang
2004-12-20 21:44 ` Nishanth Aravamudan
2004-12-20 22:40 ` Pavel Machek
2004-12-20 23:06 ` Zwane Mwaikambo
2004-12-20 23:28 ` Nigel Cunningham
2004-12-22 20:28 ` Pavel Machek
2004-12-22 21:21 ` Nigel Cunningham
2004-12-22 21:32 ` Pavel Machek
2004-12-23 0:52 ` Nigel Cunningham
2004-12-21 13:15 ` Paulo Marques
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=1101160249.7962.52.camel@desktop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=hugang@soulinfo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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