public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: swsusp3: push image reading/writing into userspace
Date: Thu, 15 Sep 2005 08:37:53 +0200	[thread overview]
Message-ID: <20050915063753.GA2691@elf.ucw.cz> (raw)
In-Reply-To: <1126749596.3987.5.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

Hi!

> > Here's prototype code for swsusp3. It seems to work for me, but don't
> > try it... yet. Code is very ugly at places, sorry, I know and will fix
> > it. This is just proof that it can be done, and that it can be done
> > without excessive ammount of code.
> 
> No comments on the code sorry. Instead I want to ask, could you please
> find a different name? swsusp3 is going to make people think that it's
> Suspend2 redesigned. Since there hasn't been a swsusp2 (so far as I
> know), how about using that name instead? At least then we'll clearly
> differentiate the two implementations and you won't confuse/irritate
> users.

swsusp2 can't be used, it is already "taken" by suspend2 (25000 hits
on google). I was actually hoping that you would release suspend4
(using swsusp3 infrastructure) :-).

I guess I could call it "uswsusp".

								Pavel
-- 
if you have sharp zaurus hardware you don't need... you know my address

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2005-09-15  6:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 22:32 swsusp3: push image reading/writing into userspace Pavel Machek
2005-09-15  1:59 ` Nigel Cunningham
2005-09-15  6:37   ` Pavel Machek [this message]
2005-09-15  7:16     ` Nigel Cunningham
2005-09-15  7:37       ` [linux-pm] " Pavel Machek
2005-09-15  9:32         ` Nigel Cunningham
2005-09-15 11:16           ` 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=20050915063753.GA2691@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=ncunningham@cyclades.com \
    /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