mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: 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: regular swsusp flamewar [was Re: [PATCH] swsusp: separate swap-writing/reading code]
Date: Tue, 28 Mar 2006 01:15:57 +0200	[thread overview]
Message-ID: <20060327231557.GB2439@elf.ucw.cz> (raw)
In-Reply-To: <200603272044.05431.ncunningham@cyclades.com>

Hi!

> > If you want faster suspend, that should be easy. You'll need *current*
> > 2.6.16-git , and userland tools from suspend.sf.net . There's HOWTO
> > that explains how to set it up. We can even do LZF these days...
> >
> > > >Currently I'm not working on any better solution.  If you can provide
> > > > any patches to implement one, please submit them, but I think they'll
> > > > have to be
> > > >tested for as long as this code, in -mm.
> > >
> > > It would be *really nice* if you guys could stop being so underhandedly
> > > nasty in every single reply to anything from Nigel.
> > >
> > > He really is trying to help, you know.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

> > Actually Rafael was *very* nice at him, I'd say. Pointing for tiny
> > inefficiencies, without patch attached is not really helpful.
...
> > I have repeatedly pointed him on ways how he can *really* help. There
> > are ways to do suspend2 in userspace these days, but Nigel refuses to
> > use them.
> 
> 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...

> encouraging people to use uswsusp when you have also warned that it might eat 
> their partitions.

uswsusp is now reasonably stable. Of course, it was dangerous some
time ago. Every software is dangerous when it is young.
								Pavel

(*) Actually I can't "disagree" with your patches because you did not
submit any, in recent history.
-- 
Picture of sleeping (Linux) penguin wanted...

  reply	other threads:[~2006-03-27 23:16 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           ` Pavel Machek [this message]
2006-03-27 23:36             ` regular swsusp flamewar [was Re: [PATCH] swsusp: separate swap-writing/reading code] 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             ` regular swsusp flamewar Harald Arnesen
2006-03-28  9:13               ` 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=20060327231557.GB2439@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=ncunningham@cyclades.com \
    --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®