From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Adam Belay <abelay@novell.com>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 0/9] PCI power management updates
Date: Tue, 06 Jun 2006 10:31:33 +1000 [thread overview]
Message-ID: <1149553894.559.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1149497136.7831.154.camel@localhost.localdomain>
On Mon, 2006-06-05 at 04:45 -0400, Adam Belay wrote:
> Hi All,
>
> This series of patches is my first pass in an effort to improve PCI
> power management. They are against 2.6.17-rc5. The changes include
> various PCI PM improvements and fixes, with a focus on low-level
> infrastructure. All code has been tested on a limited set of hardware,
> and seems to work well, but additional testing coverage will likely be
> necessary. I look forward to any suggestions or comments.
Looks really good overall, a few comments coming.
Ben.
prev parent reply other threads:[~2006-06-06 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 8:45 [PATCH 0/9] PCI power management updates Adam Belay
2006-06-06 0:31 ` Benjamin Herrenschmidt [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=1149553894.559.4.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=abelay@novell.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.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