All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Adam Belay <abelay@novell.com>,
	Linux-pm mailing list <linux-pm@lists.osdl.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: Suspend "core": what to do now ?
Date: Tue, 28 Jun 2005 16:37:41 +1000	[thread overview]
Message-ID: <1119940660.7513.24.camel@localhost> (raw)
In-Reply-To: <1119931577.5133.189.camel@gaston>

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

Hi.

On Tue, 2005-06-28 at 14:06, Benjamin Herrenschmidt wrote:
> I'm inclined to just trash all of that... but Nigel will have the same
> problem here, if I start moving the core of swsusp to arch code, he'll
> have to move the core of swsusp2 accordingly.

I have the problem that I have so little arch dependant code that it
seems silly to make the switch, but I also like the idea (as mentioned
on irc) of being able to switch between modes. (S3 for a while, then S4,
eg). To achieve something like that, it makes sense to have something
more generic, I think, that can handle these transitions. Then again,
maybe I'm just thinking of an extension to runtime PM :>

Whatever you do, I will have to work with it. I don't really see what
you're aiming at though, so I could do with a bit more brain dump if
you're willing.

Regards,

Nigel


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



      parent reply	other threads:[~2005-06-28  6:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27  5:49 Suspend "core": what to do now ? Benjamin Herrenschmidt
2005-06-27 21:23 ` Pavel Machek
2005-06-27 22:39   ` Rafael J. Wysocki
2005-06-27 22:55 ` Adam Belay
2005-06-27 23:49   ` Benjamin Herrenschmidt
2005-06-28  4:06     ` Benjamin Herrenschmidt
2005-06-28  4:58       ` Pavel Machek
2005-06-28  5:02         ` Benjamin Herrenschmidt
2005-06-28 12:44           ` Pavel Machek
2005-06-28  6:37       ` Nigel Cunningham [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=1119940660.7513.24.camel@localhost \
    --to=ncunningham@cyclades.com \
    --cc=abelay@novell.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=pavel@ucw.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.