From: Harald Arnesen <harald@skogtun.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Nigel Cunningham <ncunningham@cyclades.com>,
Mark Lord <lkml@rtr.ca>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: regular swsusp flamewar
Date: Tue, 28 Mar 2006 03:16:22 +0200 [thread overview]
Message-ID: <87mzfb9xnd.fsf@basilikum.skogtun.org> (raw)
In-Reply-To: <20060327231557.GB2439@elf.ucw.cz> (Pavel Machek's message of "Tue, 28 Mar 2006 01:15:57 +0200")
Pavel Machek <pavel@suse.cz> writes:
>> You know that I disagree that doing suspend in userspace is the
>> right
>
> You know "disagreeing" with subsystem maintainer (and everyone else
> for that matter) is not exactly helpful in getting patches merged. You
> are free to believe whatever you want, but if you disagree on
> something as fundamental as "do not put unneccessary code to kernel"
> with me, it should be no surprise that I "disagree" with your patches
> (*).
>
>> approach, and you know that current uswsusp can't do everything Suspend2 does
>> without further substantial modification. Please stop painting me as the bad
>> guy because I won't roll over and play dead for you. Please also
>> stop
>
> I'm not trying to paint you as a bad guy. But Mark said you are trying
> to help, and in that context I'd read it as "trying to help mainline
> development". And you are not doing that, you are developing your own
> suspend2 branch, that has nothing to do with mainline. I think we can
> agree on that one...
The main point for me is that suspend2 works, while mainline supspend
does not ("works": it takes less time to suspend/resume than to
shutdown/reboot).
I haven't tried uswsusp yet. Why try another out-of-kernel suspend when
suspend2 works perfectly?
--
Hilsen Harald.
next prev parent reply other threads:[~2006-03-28 1:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200603231702.k2NH2OSC006774@hera.kernel.org>
2006-03-23 21:13 ` [PATCH] swsusp: separate swap-writing/reading code Nigel Cunningham
2006-03-23 21:53 ` Rafael J. Wysocki
2006-03-23 22:48 ` Mark Lord
2006-03-23 23:39 ` Rafael J. Wysocki
2006-03-27 10:26 ` Pavel Machek
2006-03-27 10:43 ` Nigel Cunningham
2006-03-27 23:15 ` regular swsusp flamewar [was Re: [PATCH] swsusp: separate swap-writing/reading code] Pavel Machek
2006-03-27 23:36 ` Nigel Cunningham
2006-03-28 1:18 ` regular swsusp flamewar Harald Arnesen
2006-03-28 9:15 ` regular swsusp flamewar [was Re: [PATCH] swsusp: separate swap-writing/reading code] Pavel Machek
2006-03-28 9:16 ` Pavel Machek
2006-03-28 10:28 ` Nigel Cunningham
2006-03-28 1:16 ` Harald Arnesen [this message]
2006-03-28 9:13 ` regular swsusp flamewar Pavel Machek
2006-03-23 23:58 ` [PATCH] swsusp: separate swap-writing/reading code Andrew Morton
2006-03-24 0:32 ` 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=87mzfb9xnd.fsf@basilikum.skogtun.org \
--to=harald@skogtun.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=ncunningham@cyclades.com \
--cc=pavel@suse.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
all inboxes | Powered by JetHome®