From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
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>,
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: Tue, 18 May 2010 15:05:13 -0700 [thread overview]
Message-ID: <20100518150513.050bb794@virtuousgeek.org> (raw)
In-Reply-To: <201005180023.24885.rjw@sisk.pl>
On Tue, 18 May 2010 00:23:24 +0200
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> On Monday 17 May 2010, Randy Dunlap wrote:
> > On 05/16/10 12:49, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > I've just finished rewriting the PCI PM documentation. I hope I didn't forget
> > > of anything important, so please let me know if I did.
> > >
> > > Generally, please let me know what you think.
> >
> > Hi,
> >
> > It reads pretty well IMO.
> >
> > I have corrected several typos etc.
> > I have also noted a need for explaining *why* something is being done,
> > not just what is being done.
>
> Thanks a lot for the very useful comments. I did my best to address them all
> and the modified (and hopefully improved patch) is appended.
>
> > There may be a few other places where some justification is needed
> > (i.e., would be helpful).
>
> Well, in fact it is quite difficult to me to identify places where such a
> justification would be useful, because I know how all of this works. :-)
> Fortunately, the justification is usually given in the other two documents this
> one refers to.
>
Applied, thanks guys.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-05-18 22:06 UTC|newest]
Thread overview: 9+ 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 3:02 ` Randy Dunlap
2010-05-17 22:23 ` [update] " Rafael J. Wysocki
2010-05-17 22:32 ` Randy Dunlap
2010-05-17 22:32 ` Randy Dunlap
2010-05-18 22:05 ` Jesse Barnes
2010-05-18 22:05 ` Jesse Barnes [this message]
2010-05-17 22:23 ` Rafael J. Wysocki
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=20100518150513.050bb794@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=gregkh@suse.de \
--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=randy.dunlap@oracle.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 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.