From: Alon Bar-Lev <alon.barlev@gmail.com>
To: Lorenzo Colitti <lorenzo@colitti.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Nigel Cunningham <ncunningham@cyclades.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: Thu, 06 Oct 2005 10:10:40 +0000 [thread overview]
Message-ID: <4344F820.6010701@gmail.com> (raw)
In-Reply-To: <43445F51.7090403@colitti.com>
Lorenzo Colitti wrote:
> Pavel Machek wrote:
>
>> "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.
>
>
> Cheers,
> Lorenzo
>
Hello,
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
slower process but at least the interfaces suspend2 provides
will be available to users.
I understand the wish to minimize kernel mode usage... But
first you should support a decent suspend disk/suspend ram
support in Linux without forcing the user to hack his
configuration.
At my culture we say: "The enemy of the good is the best"...
Best Regards,
Alon Bar-Lev.
next prev parent reply other threads:[~2005-10-06 7:09 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 [this message]
2005-10-06 8:20 ` Pavel Machek
2005-10-09 23:41 ` Nigel Cunningham
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=4344F820.6010701@gmail.com \
--to=alon.barlev@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@colitti.com \
--cc=ncunningham@cyclades.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