public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Nigel Cunningham <ncunningham@users.sourceforge.net>
Cc: M?ns Rullg?rd <mru@kth.se>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Dropping CONFIG_PM_DISK?
Date: Mon, 1 Mar 2004 21:22:36 +0100	[thread overview]
Message-ID: <20040301202236.GF562@elf.ucw.cz> (raw)
In-Reply-To: <1078164961.4408.25.camel@laptop-linux.wpcb.org.au>

Hi!

> Forgive my ignorance, but I don't see how that could be something that
> makes suspend2 less stable than the already-merged versions. They have
> the same problem (assuming your patch hasn't been merged yet).

Okay... well...

swsusp2 is meant to be feature-full. in kernel swsusp is meant to be
stable. Perhaps swsusp2 manages to be both feature-full and stable at
same time; at that point I'm obviously doing not-too-good job.

								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2004-03-01 20:22 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1ulUA-33w-3@gated-at.bofh.it>
2004-02-29 16:17 ` Dropping CONFIG_PM_DISK? Karol Kozimor
2004-02-29 16:23   ` Pavel Machek
2004-02-29 17:32     ` Måns Rullgård
2004-02-29 18:10       ` Michael Frank
2004-02-29 21:33         ` [Swsusp-devel] " Micha Feigin
2004-03-01  2:51           ` Michael Frank
2004-03-01 11:09             ` Benjamin Herrenschmidt
2004-03-01 11:35               ` Karol Kozimor
2004-03-01 11:28                 ` Benjamin Herrenschmidt
2004-03-01 11:51                   ` Karol Kozimor
2004-03-01 12:56                     ` Martin Wickman
2004-03-01 13:22                       ` Michael Frank
2004-03-01 12:34                   ` Micha Feigin
2004-03-01 11:31                 ` Benjamin Herrenschmidt
2004-03-01 11:57                   ` Karol Kozimor
2004-03-01 22:08                     ` Benjamin Herrenschmidt
2004-03-01 11:43               ` Michael Frank
2004-03-01 11:39                 ` Benjamin Herrenschmidt
2004-03-01 12:48                   ` Michael Frank
2004-03-01 13:47                     ` Arjan van de Ven
2004-03-01 14:33                       ` Michael Frank
2004-03-01 14:38                         ` Arjan van de Ven
2004-03-01 22:10                     ` Benjamin Herrenschmidt
2004-02-29 18:10       ` Pavel Machek
2004-02-29 18:29         ` Måns Rullgård
2004-03-01  9:40           ` Pavel Machek
2004-03-01 10:08             ` Måns Rullgård
2004-03-01 10:39               ` Pavel Machek
2004-03-01  9:58                 ` Nigel Cunningham
2004-03-01 12:46                   ` Pavel Machek
2004-03-01 18:16                     ` Nigel Cunningham
2004-03-01 20:22                       ` Pavel Machek [this message]
2004-03-01 10:45               ` Michael Frank
2004-02-28 23:00 Pavel Machek
2004-02-28 23:52 ` Benjamin Herrenschmidt
2004-02-29  7:30   ` Pavel Machek
2004-02-29  7:22     ` Benjamin Herrenschmidt
2004-02-29 12:40       ` Pavel Machek
2004-03-01  9:46         ` Nigel Cunningham
2004-03-01 12:40 ` Romano Giannetti

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=20040301202236.GF562@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@kth.se \
    --cc=ncunningham@users.sourceforge.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