From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: First working version of suspend-to-RAM
Date: Mon, 29 Apr 2002 09:51:22 +0200 [thread overview]
Message-ID: <20020429075122.GD2740@come.alcove-fr> (raw)
In-Reply-To: <20020428211754.GA9679@elf.ucw.cz>
On Sun, Apr 28, 2002 at 11:17:54PM +0200, Pavel Machek wrote:
> Seems that suspend-to-ram needs stopping all processes, too. I had to
> combine S3 patches with swsusp to make it possible. That means that
> you get suspend-to-disk for free with the bundle ;-).
Could you please reread Documentation/SubmittingPatches, especially
these 2 points:
* No MIME, no links, no compression, no attachments. Just plain text.
* usage of 'dontdiff'
I'm sure this will help people try out your patch and give you
feedback...
Thanks,
Stelian.
--
Stelian Pop <stelian.pop@fr.alcove.com>
Alcove - http://www.alcove.com
next prev parent reply other threads:[~2002-04-29 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-28 21:17 First working version of suspend-to-RAM Pavel Machek
2002-04-29 7:51 ` Stelian Pop [this message]
2002-04-29 10:21 ` Alan Cox
2002-04-29 9:59 ` David S. Miller
2002-04-29 10:05 ` Stelian Pop
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=20020429075122.GD2740@come.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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