From: Nigel Cunningham <ncunningham@cyclades.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Add some hooks to generic suspend code
Date: Wed, 01 Jun 2005 19:36:55 +1000 [thread overview]
Message-ID: <1117618614.14386.2057.camel@localhost> (raw)
In-Reply-To: <20050601090622.GB6693@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 291 bytes --]
Hi.
On Wed, 2005-06-01 at 19:06, Pavel Machek wrote:
> Seems like lots of stuff is going to happen in pm post-2.6.12: I'd
> like to finally fix pm_message_t, too...
Speaking of which, how do you want to move forward with the refrigerator
patches I sent you a while back?
Regards,
Nigel
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [RFC] Add some hooks to generic suspend code
Date: Wed, 01 Jun 2005 19:36:55 +1000 [thread overview]
Message-ID: <1117618614.14386.2057.camel@localhost> (raw)
In-Reply-To: <20050601090622.GB6693@elf.ucw.cz>
Hi.
On Wed, 2005-06-01 at 19:06, Pavel Machek wrote:
> Seems like lots of stuff is going to happen in pm post-2.6.12: I'd
> like to finally fix pm_message_t, too...
Speaking of which, how do you want to move forward with the refrigerator
patches I sent you a while back?
Regards,
Nigel
next prev parent reply other threads:[~2005-06-01 9:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 7:29 [RFC] Add some hooks to generic suspend code Benjamin Herrenschmidt
2005-05-31 7:29 ` Benjamin Herrenschmidt
2005-05-31 10:13 ` [linux-pm] " Pavel Machek
2005-05-31 14:44 ` Benjamin Herrenschmidt
2005-05-31 14:44 ` [linux-pm] " Benjamin Herrenschmidt
2005-05-31 21:25 ` Pavel Machek
2005-05-31 21:25 ` [linux-pm] " Pavel Machek
2005-05-31 23:31 ` Benjamin Herrenschmidt
2005-05-31 23:31 ` [linux-pm] " Benjamin Herrenschmidt
2005-06-01 8:13 ` Pavel Machek
2005-06-01 8:13 ` [linux-pm] " Pavel Machek
2005-06-01 8:34 ` Benjamin Herrenschmidt
2005-06-01 8:34 ` [linux-pm] " Benjamin Herrenschmidt
2005-06-01 9:06 ` Pavel Machek
2005-06-01 9:06 ` [linux-pm] " Pavel Machek
2005-06-01 9:36 ` Nigel Cunningham [this message]
2005-06-01 9:36 ` Nigel Cunningham
2005-06-01 9:55 ` Pavel Machek
2005-06-01 9:55 ` [linux-pm] " Pavel Machek
2005-06-01 10:38 ` Benjamin Herrenschmidt
2005-06-01 10:38 ` [linux-pm] " Benjamin Herrenschmidt
2005-06-02 16:21 ` Stefan Seyfried
2005-06-02 22:18 ` Benjamin Herrenschmidt
2005-06-02 22:18 ` Benjamin Herrenschmidt
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=1117618614.14386.2057.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=linux-kernel@vger.kernel.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.