From: Nigel Cunningham <ncunningham@cyclades.com>
To: Daniel Goller <morfic@gentoo.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] swsusp3: push image reading/writing into userspace
Date: Thu, 15 Sep 2005 12:24:19 +1000 [thread overview]
Message-ID: <1126751058.3987.10.camel@localhost> (raw)
In-Reply-To: <200509142113.03763.morfic@gentoo.org>
Hi.
On Thu, 2005-09-15 at 12:13, Daniel Goller wrote:
> 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)
Yes, they do sometimes. But that's not right since 'sw' is at least
sometimes treated as an abbreviation for swap. Suspend2 isn't limited to
writing to swap. That (along with the fact that swsusp is an ugly
acronym) is the reason why I've tried to push away from using that term.
> > 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
If they're clearly differentiated, that shouldn't be a problem. In fact,
it would help differentiate them.
> Just a thought,
Thanks!
Nigel
> Daniel
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
next prev parent reply other threads:[~2005-09-15 2:24 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
2005-09-15 2:24 ` Nigel Cunningham [this message]
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=1126751058.3987.10.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morfic@gentoo.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