From: Nigel Cunningham <ncunningham@cyclades.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Alon Bar-Lev <alon.barlev@gmail.com>,
Lorenzo Colitti <lorenzo@colitti.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [swsusp] separate snapshot functionality to separate file
Date: Mon, 10 Oct 2005 09:41:22 +1000 [thread overview]
Message-ID: <1128901281.4747.7.camel@localhost> (raw)
In-Reply-To: <20051006082050.GA10865@openzaurus.ucw.cz>
Hi Pavel.
On Thu, 2005-10-06 at 18:20, Pavel Machek wrote:
> Hi!
>
> > >>"Cool, so you have done 100% of work and now it is stable, fast and
> > >>tested. You only need to do 200% more work to get it merged".
> > >>
> > >>Merging into kernel is not easy, sorry.
> > >>
> > >It works, it's fast, it's stable, and it does what users want.
> > >That's a strong combination. It would be really good if you could
> > >work together to merge it.
>
> > I've read this thread...
> > And I want to join this request...
> >
> > It might be that suspend2 is not the best solution, but
> > maybe if you merge it and then work together in order to
> > maximize the use of user space at next version, it will be
>
> Merge 10000 lines of code, only to drop them in next version?
You're assuming your code would get merged.
More than that, though, let me be bold enough to say that your version
has quite a lot of development to do in order to begin to approach the
level of Suspend2. If and when it achieves that, I'll happily stop
maintaining Suspend2 - after all, I've always said I'm just a user who
wants to suspend. In the meantime, though, I'm happy to carry that can
while you're developing your userspace implementation. That way, users
can have the best of both worlds - a stable, reliable, fast and mature
implementation in kernel space while you're getting userspace working,
and then whatever advantages you bring once your version becomes an
improved version of Suspend2.
Regards,
Nigel
next prev parent reply other threads:[~2005-10-09 23:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 23:13 [swsusp] separate snapshot functionality to separate file Pavel Machek
2005-10-03 21:39 ` Rafael J. Wysocki
2005-10-03 23:17 ` Pavel Machek
2005-10-04 15:11 ` Rafael J. Wysocki
2005-10-04 20:53 ` Pavel Machek
2005-10-04 22:34 ` Nigel Cunningham
2005-10-05 8:41 ` Pavel Machek
2005-10-05 21:21 ` Lorenzo Colitti
2005-10-05 22:21 ` Nigel Cunningham
2005-10-05 22:44 ` Pavel Machek
2005-10-05 22:54 ` Lorenzo Colitti
2005-10-05 22:57 ` Pavel Machek
2005-10-05 23:00 ` Pavel Machek
2005-10-05 23:18 ` Lorenzo Colitti
2005-10-06 10:10 ` Alon Bar-Lev
2005-10-06 8:20 ` Pavel Machek
2005-10-09 23:41 ` Nigel Cunningham [this message]
2005-10-04 22:47 ` Rafael J. Wysocki
2005-10-05 0:06 ` Pavel Machek
2005-10-05 8:20 ` Rafael J. Wysocki
2005-10-05 8:33 ` Pavel Machek
2005-10-06 8:23 ` Rafael J. Wysocki
2005-10-06 10:42 ` Pavel Machek
2005-10-06 13:29 ` Rafael J. Wysocki
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=1128901281.4747.7.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=akpm@osdl.org \
--cc=alon.barlev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@colitti.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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