From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Nigel Cunningham <nigel@nigel.suspend2.net>
Cc: Bill Davidsen <davidsen@tmr.com>,
nigel@suspend2.net, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Suspend2 is getting a new name.
Date: Tue, 3 Jul 2007 15:34:05 +0200 [thread overview]
Message-ID: <200707031534.06350.rjw@sisk.pl> (raw)
In-Reply-To: <200707030808.26802.nigel@nigel.suspend2.net>
Hi,
On Tuesday, 3 July 2007 00:08, Nigel Cunningham wrote:
> Hi.
>
> On Tuesday 03 July 2007 05:18:39 Bill Davidsen wrote:
> > Nigel Cunningham wrote:
> > > Hi all.
> > >
> > > Suspend2's name is changing to "TuxOnIce".
> > >
> > > This is for a couple of reasons:
> > >
> > > In recent discussions on LKML, the point was made that the word "Suspend"
> is
> > > confusing. It is used to refer to both suspending to disk and suspending
> to
> > > ram. Life will be simpler if we more clearly differentiate the two.
> > >
> > > The name Suspend2 came about a couple of years ago when we made the 2.0
> > > release and started self-hosting. If we ever get to a 3.0 release, the
> name
> > > could become even more confusing! (And there are already problems with
> people
> > > confusing the name with swsusp and talking about uswsusp as version 3!).
> > >
> > > http://www.suspend2.net is still working at the moment, but we'll shift to
> > > http://www.tuxonice.net over the next while. The wiki and bugzilla are
> > > already done; email will remain on suspend2.net for a little while and git
> > > trees will be renamed at the time of the next stable release.
> > >
> > I guess this is "good news, bad news" time. The good news is that the
> > "suspend with working resume" project is still active, the bad news is
> > that making provisions for long term out of mainline operation sounds as
> > if you have no hope of getting this code into the mainline kernel. :-(
>
> Let's not turn this into a flamewar, please. This is just a name change,
> nothing more.
>
> As far as I know, the desire on Rafael's part and mine is still to get at
> least some of the functionality merged. The only reason this isn't happening
> yet is that we're both busy with other aspects of the work. Rafael is
> focussing on infrastructure issues, I'm focussing on minimising the diff and
> finishing off cleaning up and adding comments to functions.
That's correct, thanks for saying this!
My first target is to introduce a framework allowing drivers to have different
callbacks for hibernation and suspend. Unfortunately, that turned out to
require quite a lot of work - and time - to do.
Greetings,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
prev parent reply other threads:[~2007-07-03 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 7:30 Nigel Cunningham
2007-07-02 7:39 ` Jan Engelhardt
2007-07-02 8:10 ` Nigel Cunningham
2007-07-02 8:23 ` Satyam Sharma
2007-07-04 17:59 ` Pavel Machek
2007-07-02 8:30 ` Fabio Comolli
2007-07-02 8:35 ` Oliver Neukum
2007-07-02 12:16 ` Renato S. Yamane
2007-07-02 18:41 ` Alon Bar-Lev
2007-07-02 19:11 ` Fabio Comolli
2007-07-03 0:47 ` Mail List
2007-07-02 19:18 ` Bill Davidsen
2007-07-02 22:08 ` Nigel Cunningham
2007-07-03 13:34 ` Rafael J. Wysocki [this message]
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=200707031534.06350.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=nigel@suspend2.net \
/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
all inboxes | Powered by JetHome®