From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Patrick Mochel <mochel@digitalimplant.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Re: Concerns about our pci_{save,restore}_state()
Date: Fri, 29 Oct 2004 08:44:22 +1000 [thread overview]
Message-ID: <1099003462.29693.66.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.50.0410280149140.13935-100000@monsoon.he.net>
On Thu, 2004-10-28 at 01:50 -0700, Patrick Mochel wrote:
> What's wrong with that? They would be simple and straightforward, and
> could probably work to remove many of the quirks, too..
Right.
ben.
next prev parent reply other threads:[~2004-10-28 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 4:06 Concerns about our pci_{save,restore}_state() Benjamin Herrenschmidt
2004-10-25 6:11 ` Jeff Garzik
2004-10-25 6:24 ` Benjamin Herrenschmidt
2004-10-25 8:32 ` Arjan van de Ven
2004-10-25 9:04 ` Benjamin Herrenschmidt
2004-10-28 8:50 ` [linux-pm] " Patrick Mochel
2004-10-28 22:44 ` Benjamin Herrenschmidt [this message]
2004-10-28 21:31 ` Greg KH
2004-10-28 22:50 ` 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=1099003462.29693.66.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=mochel@digitalimplant.org \
/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