linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Changbin Du <changbin.du@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Changbin Du <changbin.du@gmail.com>
Subject: [PATCH v3 06/12] Documentation: PCI: convert acpi-info.txt to reST
Date: Tue,  9 Apr 2019 23:56:20 +0800	[thread overview]
Message-ID: <20190409155626.6049-7-changbin.du@gmail.com> (raw)
In-Reply-To: <20190409155626.6049-1-changbin.du@gmail.com>

This converts the plain text documentation to reStructuredText format and
add it to Sphinx TOC tree. No essential content change.

Signed-off-by: Changbin Du <changbin.du@gmail.com>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
---
 Documentation/PCI/{acpi-info.txt => acpi-info.rst} | 11 ++++++++---
 Documentation/PCI/index.rst                        |  1 +
 2 files changed, 9 insertions(+), 3 deletions(-)
 rename Documentation/PCI/{acpi-info.txt => acpi-info.rst} (97%)

diff --git a/Documentation/PCI/acpi-info.txt b/Documentation/PCI/acpi-info.rst
similarity index 97%
rename from Documentation/PCI/acpi-info.txt
rename to Documentation/PCI/acpi-info.rst
index 3ffa3b03970e..f7dabb7ca255 100644
--- a/Documentation/PCI/acpi-info.txt
+++ b/Documentation/PCI/acpi-info.rst
@@ -1,4 +1,8 @@
-		ACPI considerations for PCI host bridges
+.. SPDX-License-Identifier: GPL-2.0
+
+========================================
+ACPI considerations for PCI host bridges
+========================================
 
 The general rule is that the ACPI namespace should describe everything the
 OS might use unless there's another way for the OS to find it [1, 2].
@@ -135,8 +139,9 @@ address always corresponds to bus 0, even if the bus range below the bridge
 
     Extended Address Space Descriptor (.4)
     General Flags: Bit [0] Consumer/Producer:
-	1–This device consumes this resource
-	0–This device produces and consumes this resource
+
+        * 1 – This device consumes this resource
+        * 0 – This device produces and consumes this resource
 
 [5] ACPI 6.2, sec 19.6.43:
     ResourceUsage specifies whether the Memory range is consumed by
diff --git a/Documentation/PCI/index.rst b/Documentation/PCI/index.rst
index 1b25bcc1edca..c877a369481d 100644
--- a/Documentation/PCI/index.rst
+++ b/Documentation/PCI/index.rst
@@ -12,3 +12,4 @@ Linux PCI Bus Subsystem
    PCIEBUS-HOWTO
    pci-iov-howto
    MSI-HOWTO
+   acpi-info
-- 
2.20.1


  parent reply	other threads:[~2019-04-09 15:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 15:56 [PATCH v3 00/12] Include linux PCI docs into Sphinx TOC tree Changbin Du
2019-04-09 15:56 ` [PATCH v3 01/12] Documentation: add Linux PCI to " Changbin Du
2019-04-09 15:56 ` [PATCH v3 02/12] Documentation: PCI: convert pci.txt to reST Changbin Du
2019-04-09 15:56 ` [PATCH v3 03/12] Documentation: PCI: convert PCIEBUS-HOWTO.txt " Changbin Du
2019-04-09 15:56 ` [PATCH v3 04/12] Documentation: PCI: convert pci-iov-howto.txt " Changbin Du
2019-04-09 15:56 ` [PATCH v3 05/12] Documentation: PCI: convert MSI-HOWTO.txt " Changbin Du
2019-04-09 15:56 ` Changbin Du [this message]
2019-04-09 15:56 ` [PATCH v3 07/12] Documentation: PCI: convert pci-error-recovery.txt " Changbin Du
2019-04-09 15:56 ` [PATCH v3 08/12] Documentation: PCI: convert pcieaer-howto.txt " Changbin Du
2019-04-09 15:56 ` [PATCH v3 09/12] Documentation: PCI: convert endpoint/pci-endpoint.txt " Changbin Du
2019-04-09 15:56 ` [PATCH v3 10/12] Documentation: PCI: convert endpoint/pci-endpoint-cfs.txt " Changbin Du
2019-04-09 15:56 ` [PATCH v3 11/12] Documentation: PCI: convert endpoint/pci-test-function.txt " Changbin Du
2019-04-09 15:56 ` [PATCH v3 12/12] Documentation: PCI: convert endpoint/pci-test-howto.txt " Changbin Du

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=20190409155626.6049-7-changbin.du@gmail.com \
    --to=changbin.du@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).