From: Daniel Goller <morfic@gentoo.org>
To: ncunningham@cyclades.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] swsusp3: push image reading/writing into userspace
Date: Wed, 14 Sep 2005 21:13:02 -0500 [thread overview]
Message-ID: <200509142113.03763.morfic@gentoo.org> (raw)
In-Reply-To: <1126749596.3987.5.camel@localhost>
On Wednesday 14 September 2005 08:59 pm, Nigel Cunningham wrote:
> 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),
swsusp2 seems to be the common/trivial name for suspend2 (at least while
struggling to get any kind of suspend working here, helpful people have
refered to suspend2 as swsusp2)
> how about using that name instead? At least then we'll clearly
> differentiate the two implementations and you won't confuse/irritate
> users.
if he would use that people would get quite confused and not know if people
mean your suspend2 or his swsusp2
Just a thought,
Daniel
next prev parent reply other threads:[~2005-09-15 2:13 UTC|newest]
Thread overview: 9+ 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 ` [linux-pm] " Nigel Cunningham
2005-09-15 2:13 ` Daniel Goller [this message]
2005-09-15 2:24 ` Nigel Cunningham
2005-09-15 6:37 ` Pavel Machek
2005-09-15 7:16 ` Nigel Cunningham
2005-09-15 7:37 ` 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=200509142113.03763.morfic@gentoo.org \
--to=morfic@gentoo.org \
--cc=linux-kernel@vger.kernel.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