From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Matthew Garrett <mjg@redhat.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [update] Re: [RFC][PATCH] PM / PCI: Update PCI power management documentation
Date: Mon, 17 May 2010 15:32:17 -0700 [thread overview]
Message-ID: <4BF1C3F1.3000904@oracle.com> (raw)
In-Reply-To: <201005180023.24885.rjw@sisk.pl>
On 05/17/10 15:23, Rafael J. Wysocki wrote:
> ---
> From: Rafael J. Wysocki <rjw@sisk.pl>
> Subject: PM / PCI: Update PCI power management documentation
>
> The PCI power management document, Documentation/power/pci.txt, is
> outdated and partially inaccurate. It also is missing some important
> information about the power management of PCI device. Rewrite it to
> make it more up to date and more complete.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Thanks for the updates.
Reviewed-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
> Documentation/power/pci.txt | 1308 ++++++++++++++++++++++++++++++++++----------
> 1 file changed, 1017 insertions(+), 291 deletions(-)
>
> Index: linux-2.6/Documentation/power/pci.txt
> ===================================================================
> --- linux-2.6.orig/Documentation/power/pci.txt
> +++ linux-2.6/Documentation/power/pci.txt
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-05-17 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 19:49 [RFC][PATCH] PM / PCI: Update PCI power management documentation Rafael J. Wysocki
2010-05-17 3:02 ` Randy Dunlap
2010-05-17 22:23 ` [update] " Rafael J. Wysocki
2010-05-17 22:32 ` Randy Dunlap [this message]
2010-05-18 22:05 ` Jesse Barnes
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=4BF1C3F1.3000904@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mjg@redhat.com \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).