linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Don Dutile <ddutile@redhat.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Bjorn Mork <bjorn@mork.no>
Subject: Re: [RFC] PCI/PM: Add ABI document for sysfs file d3cold_allowed
Date: Tue, 31 Jul 2012 09:50:23 -0400	[thread overview]
Message-ID: <5017E29F.9010609@redhat.com> (raw)
In-Reply-To: <1343704341.2591.8.camel@yhuang-dev>

On 07/30/2012 11:12 PM, Huang Ying wrote:
> Hi, Don,
>
> Thanks for your comments.
>
> On Mon, 2012-07-30 at 14:03 -0400, Don Dutile wrote:
>> On 07/27/2012 04:07 AM, Huang Ying wrote:
>>> This patch adds ABI document for the following sysfs file:
>>>
>>> /sys/bus/pci/devices/.../d3cold_allowed
>>>
>>> Signed-off-by: Huang Ying<ying.huang@intel.com>
>>> ---
>>>    Documentation/ABI/testing/sysfs-bus-pci |   12 ++++++++++++
>>>    1 file changed, 12 insertions(+)
>>>
>>> --- a/Documentation/ABI/testing/sysfs-bus-pci
>>> +++ b/Documentation/ABI/testing/sysfs-bus-pci
>>> @@ -210,3 +210,15 @@ Users:
>>>    		firmware assigned instance number of the PCI
>>>    		device that can help in understanding the firmware
>>>    		intended order of the PCI device.
>>> +
>>> +What:		/sys/bus/pci/devices/.../d3cold_allowed
>>> +Date:		July 2012
>>> +Contact:	Huang Ying<ying.huang@intel.com>
>>> +Description:
>>> +		d3cold_allowed is bit to control whether the corresponding PCI
>>> +		device can be put into D3Cold state.  If it is cleared, the
>>> +		device will never be put into D3Cold state.  If it is set, the
>>> +		device may be put into D3Cold state if other requirement are
>> did you mean 'requirements' here? -------------------------------^
>> or is there only 1 other requirement?
>
> I mean requirements here.
>
>>
>>> +		satisfied too.  Reading this attribute will show the current
>>> +		value of d3cold_allowed bit.  Writting this attribute will set
>> spell checker says 'Writing' --------------------^
>
> Sorry about my poor English and I should have spell checked it before
> sending out.
>
no problem!  I figured since you were making the extra
effort to add the documentation, we might as well make it clear.
Thanks for the update.

> Best Regards,
> Huang Ying
>
>


      reply	other threads:[~2012-07-31 13:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27  8:07 [RFC] PCI/PM: Add ABI document for sysfs file d3cold_allowed Huang Ying
2012-07-27 19:07 ` Rafael J. Wysocki
2012-07-30 18:03 ` Don Dutile
2012-07-31  3:12   ` Huang Ying
2012-07-31 13:50     ` Don Dutile [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=5017E29F.9010609@redhat.com \
    --to=ddutile@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=bjorn@mork.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=ying.huang@intel.com \
    /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).