From: Nigel Cunningham <ncunningham@cyclades.com>
To: Pavel Machek <pavel@ucw.cz>
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 11:59:56 +1000 [thread overview]
Message-ID: <1126749596.3987.5.camel@localhost> (raw)
In-Reply-To: <20050914223206.GA2376@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
Hi Pavel.
On Thu, 2005-09-15 at 08:32, Pavel Machek wrote:
> 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.
Regards,
Nigel
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: [linux-pm] swsusp3: push image reading/writing into userspace
Date: Thu, 15 Sep 2005 11:59:56 +1000 [thread overview]
Message-ID: <1126749596.3987.5.camel@localhost> (raw)
In-Reply-To: <20050914223206.GA2376@elf.ucw.cz>
Hi Pavel.
On Thu, 2005-09-15 at 08:32, Pavel Machek wrote:
> 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.
Regards,
Nigel
next prev parent reply other threads:[~2005-09-15 1:59 UTC|newest]
Thread overview: 15+ 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-14 22:32 ` Pavel Machek
2005-09-15 1:59 ` Nigel Cunningham [this message]
2005-09-15 1:59 ` [linux-pm] " Nigel Cunningham
2005-09-15 2:13 ` Daniel Goller
2005-09-15 2:24 ` Nigel Cunningham
2005-09-15 6:37 ` Pavel Machek
2005-09-15 6:37 ` [linux-pm] " Pavel Machek
2005-09-15 7:16 ` Nigel Cunningham
2005-09-15 7:16 ` [linux-pm] " Nigel Cunningham
2005-09-15 7:37 ` Pavel Machek
2005-09-15 9:32 ` Nigel Cunningham
2005-09-15 9:32 ` [linux-pm] " Nigel Cunningham
2005-09-15 11:16 ` Pavel Machek
2005-09-15 11:16 ` [linux-pm] " 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=1126749596.3987.5.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.