public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/RFT] suspend from userland
Date: Fri, 9 Dec 2005 00:04:07 +0100	[thread overview]
Message-ID: <20051208230407.GB3970@elf.ucw.cz> (raw)
In-Reply-To: <200512082352.07659.rjw@sisk.pl>

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]

Hi!

> > I'd like to get some testing and comments on this. I know that
> > userland part is messy and will not work on x86-64 etc, and I should
> > obviously remove some extra printk's... but otherwise it should be okay.
> > 
> > Testing would be nice, too, but be a bit careful. It should not be
> > more dangerous than /sys/power/resume, but... If you suspect something
> > unusual, be sure to force fsck.
> 
> Could we please postpone it for some time?

Well, it is probably not going into -mm before your changes are in
mainline. That means 2.6.17 earliest.

> First, the patch doesn't apply to the current -mm and the userland part is
> incompatible with the code there to the extent of a serious breakage
> (let alone the x86-64 issue).

Of course I'm going to fix up breakage before the merge. At least all
the kernel parts and enough userland to test that it still works.

> Second, if I had some time to get my solution ready, we could compare the
> alternatives instead of just discussing one of them.

Well, I'm trying to gently push you. I'd like to get some solution in
1-2 months timeframe, so that work on userland parts can start.
									Pavel
-- 
Thanks, Sharp!

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2005-12-08 23:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-07  1:17 [RFC/RFT] suspend from userland Pavel Machek
2005-12-08 22:52 ` Rafael J. Wysocki
2005-12-08 23:04   ` Pavel Machek [this message]

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=20051208230407.GB3970@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --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