public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Bj?rn Mork <bmork@dod.no>, linux-kernel@vger.kernel.org
Subject: Re: Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1
Date: Tue, 22 Nov 2005 15:37:36 -0500	[thread overview]
Message-ID: <d120d5000511221237v51347b8fpe6292514e4eeca25@mail.gmail.com> (raw)
In-Reply-To: <d120d5000511221108h4ada6012kbf0b9d5166381904@mail.gmail.com>

On 11/22/05, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> On 11/22/05, Pavel Machek <pavel@suse.cz> wrote:
> > Hi!
> >
> > > > > If a clueless users voice counts for anything: I couldn't agree more.
> > > > >
> > > > > A failed resume is a near catastrophy if you use and trust swsusp. And
> > > > > how could it ever be useful if you don't?
> > > >
> > > > Failed resume is only as bad as powerfail.
> > >
> > > So? I don't like powerfails either. Could you please answer this
> > > question - what pros of having resume process time out do you
> > > envision? What problems does it help to solve?
> >
> > No advantages, really.. except that it keeps suspend and resume paths
> > similar, and keeps the code simple. I'll want to call this from
> > userland and I'd hate to have two different calls or call with
> > parameter.
> >
>
> Passing a parameter from userspace - is it so hard? Oh well, if you
> prefer to leave this as a time bomb ready to explode - so be it.
>

I think my words were a tad too strong. I apologize.

--
Dmitry

  reply	other threads:[~2005-11-22 20:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-12 13:39 Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1 Bjørn Mork
2005-11-12 15:23 ` Dmitry Torokhov
2005-11-12 20:01   ` Pavel Machek
2005-11-12 20:39   ` Pavel Machek
2005-11-13  1:53     ` Dmitry Torokhov
2005-11-13 10:09       ` Bjørn Mork
2005-11-17 21:57 ` Dmitry Torokhov
2005-11-18  9:37   ` Bjørn Mork
2005-11-18 11:40   ` Pavel Machek
2005-11-18 11:49     ` Bjørn Mork
2005-11-18 18:31       ` Pavel Machek
2005-11-18 23:32         ` Dmitry Torokhov
2005-11-19 23:48           ` Pavel Machek
2005-11-22  5:26             ` Dmitry Torokhov
2005-11-22  8:57               ` Bjørn Mork
2005-11-22 17:46                 ` Pavel Machek
2005-11-22 18:41                   ` Bjørn Mork
2005-11-22 18:53                     ` Pavel Machek
2005-11-22 18:45                   ` Dmitry Torokhov
2005-11-22 18:59                     ` Pavel Machek
2005-11-22 19:08                       ` Dmitry Torokhov
2005-11-22 20:37                         ` Dmitry Torokhov [this message]
2005-11-22 18:47               ` Pavel Machek
2005-11-22 22:15                 ` Rafael J. Wysocki
2005-11-22 22:51                   ` Pavel Machek
2005-11-23 10:09                     ` Bjørn Mork
2005-11-23 12:01                       ` Pavel Machek
2005-11-23 13:14                         ` Bjørn Mork
2005-11-23 13:25                           ` Pavel Machek
2005-11-23 10:53                     ` Rafael J. Wysocki
2005-11-18 13:46   ` Bernd Donner
  -- strict thread matches above, loose matches on Subject: below --
2005-11-13  3:08 Bernd Donner
2005-11-13 12:13 ` Jacek Kawa

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=d120d5000511221237v51347b8fpe6292514e4eeca25@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=bmork@dod.no \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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