From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@linuxmail.org>
Cc: hugang@soulinfo.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: swsusp bigdiff [was Re: [PATCH] Software Suspend split to two stage V2.]
Date: Wed, 22 Dec 2004 22:32:08 +0100 [thread overview]
Message-ID: <20041222213208.GA23761@elf.ucw.cz> (raw)
In-Reply-To: <1103750502.10045.27.camel@desktop.cunninghams>
Hi!
> > Well, we are starting with small steps... And since nobody knows how
> > to do one-device-suspend properly, we started with fixing system
> > suspend first.
> >
> > Passing structure instead of u32 should make one-device-suspend easier
> > in future... Hopefully.
>
> I could spend some time working on a proposal for this, if you like. It
> would probably do me good in preparation for my presentation on 2.6 PM
> (in general) at the CELF Linux Form next month.
You mean proposal for one-device-suspend? Well, I'd really like to
have whole machine case working, first... Then, yes, that would be
nice. It needs to be discussed at linux-pm list.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2004-12-22 21:32 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
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 [this message]
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=20041222213208.GA23761@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=hugang@soulinfo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@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