From: Bjorn Helgaas <helgaas@kernel.org>
To: Changbin Du <changbin.du@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/12] Include linux PCI docs into Sphinx TOC tree
Date: Wed, 3 Apr 2019 11:58:58 -0500 [thread overview]
Message-ID: <20190403165858.GA67241@google.com> (raw)
In-Reply-To: <20190403154955.12096-1-changbin.du@gmail.com>
On Wed, Apr 03, 2019 at 11:49:43PM +0800, Changbin Du wrote:
> Hi all,
>
> The kernel now uses Sphinx to generate intelligent and beautiful documentation
> from reStructuredText files. I converted most of the Linux PCI docs to rst
> format in this serias.
>
> For you to preview, please visit below url:
> http://www.bytemem.com:8080/kernel-doc/PCI/index.html
>
> Thank you!
>
> v2: trivial style update.
>
> Changbin Du (12):
> Documentation: add Linux PCI to Sphinx TOC tree
> Documentation: PCI: convert PCI/pci.txt to reST format
> Documentation: PCI: convert PCI/PCIEBUS-HOWTO.txt to reST format
> Documentation: PCI: convert PCI/pci-iov-howto.txt to reST format
> Documentation: PCI: convert PCI/MSI-HOWTO.txt to reST format
> Documentation: PCI: convert PCI/acpi-info.txt to reST format
> Documentation: PCI: convert PCI/pci-error-recovery.txt to reST format
> Documentation: PCI: convert PCI/pcieaer-howto.txt to reST format
> Documentation: PCI: convert PCI/endpoint/pci-endpoint.txt to reST
> format
> Documentation: PCI: convert PCI/endpoint/pci-endpoint-cfs.txt to reST
> format
> Documentation: PCI: convert PCI/endpoint/pci-test-function.txt to reST
> format
> Documentation: PCI: convert PCI/endpoint/pci-test-howto.txt to reST
> format
Thanks for doing that! If you have occasion to revise this for any
other reason, I actually suggested this:
Documentation: PCI: Convert pci.txt to reST
Documentation: PCI: Convert endpoint/pci-endpoint.txt to reST
which (a) Capitalizes the "Convert" and (b) omits the "PCI/" prefix
because it seems redundant.
By coincidence I happened across this post that talks about why I care
about these seemingly trivial things:
https://chris.beams.io/posts/git-commit/
But with or without that change, for the whole series:
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> .../PCI/{MSI-HOWTO.txt => MSI-HOWTO.rst} | 83 +++---
> .../{PCIEBUS-HOWTO.txt => PCIEBUS-HOWTO.rst} | 140 +++++----
> .../PCI/{acpi-info.txt => acpi-info.rst} | 11 +-
> Documentation/PCI/endpoint/index.rst | 13 +
> ...-endpoint-cfs.txt => pci-endpoint-cfs.rst} | 99 ++++---
> .../{pci-endpoint.txt => pci-endpoint.rst} | 95 ++++---
> ...est-function.txt => pci-test-function.rst} | 32 ++-
> ...{pci-test-howto.txt => pci-test-howto.rst} | 81 ++++--
> Documentation/PCI/index.rst | 18 ++
> ...or-recovery.txt => pci-error-recovery.rst} | 178 ++++++------
> .../{pci-iov-howto.txt => pci-iov-howto.rst} | 161 ++++++-----
> Documentation/PCI/{pci.txt => pci.rst} | 267 +++++++++---------
> .../{pcieaer-howto.txt => pcieaer-howto.rst} | 110 +++++---
> Documentation/index.rst | 1 +
> MAINTAINERS | 2 +-
> 15 files changed, 754 insertions(+), 537 deletions(-)
> rename Documentation/PCI/{MSI-HOWTO.txt => MSI-HOWTO.rst} (88%)
> rename Documentation/PCI/{PCIEBUS-HOWTO.txt => PCIEBUS-HOWTO.rst} (70%)
> rename Documentation/PCI/{acpi-info.txt => acpi-info.rst} (97%)
> create mode 100644 Documentation/PCI/endpoint/index.rst
> rename Documentation/PCI/endpoint/{pci-endpoint-cfs.txt => pci-endpoint-cfs.rst} (64%)
> rename Documentation/PCI/endpoint/{pci-endpoint.txt => pci-endpoint.rst} (82%)
> rename Documentation/PCI/endpoint/{pci-test-function.txt => pci-test-function.rst} (84%)
> rename Documentation/PCI/endpoint/{pci-test-howto.txt => pci-test-howto.rst} (78%)
> create mode 100644 Documentation/PCI/index.rst
> rename Documentation/PCI/{pci-error-recovery.txt => pci-error-recovery.rst} (80%)
> rename Documentation/PCI/{pci-iov-howto.txt => pci-iov-howto.rst} (63%)
> rename Documentation/PCI/{pci.txt => pci.rst} (78%)
> rename Documentation/PCI/{pcieaer-howto.txt => pcieaer-howto.rst} (81%)
>
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-04-03 16:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 15:49 [PATCH v2 00/12] Include linux PCI docs into Sphinx TOC tree Changbin Du
2019-04-03 15:49 ` [PATCH v2 01/12] Documentation: add Linux PCI to " Changbin Du
2019-04-03 15:49 ` [PATCH v2 02/12] Documentation: PCI: convert PCI/pci.txt to reST format Changbin Du
2019-04-03 15:49 ` [PATCH v2 03/12] Documentation: PCI: convert PCI/PCIEBUS-HOWTO.txt " Changbin Du
2019-04-03 15:49 ` [PATCH v2 04/12] Documentation: PCI: convert PCI/pci-iov-howto.txt " Changbin Du
2019-04-03 15:49 ` [PATCH v2 05/12] Documentation: PCI: convert PCI/MSI-HOWTO.txt " Changbin Du
2019-04-03 15:49 ` [PATCH v2 06/12] Documentation: PCI: convert PCI/acpi-info.txt " Changbin Du
2019-04-03 15:49 ` [PATCH v2 07/12] Documentation: PCI: convert PCI/pci-error-recovery.txt " Changbin Du
2019-04-03 15:49 ` [PATCH v2 08/12] Documentation: PCI: convert PCI/pcieaer-howto.txt " Changbin Du
2019-04-03 15:49 ` [PATCH v2 09/12] Documentation: PCI: convert PCI/endpoint/pci-endpoint.txt " Changbin Du
2019-04-03 15:49 ` [PATCH v2 10/12] Documentation: PCI: convert PCI/endpoint/pci-endpoint-cfs.txt " Changbin Du
2019-04-03 15:49 ` [PATCH v2 11/12] Documentation: PCI: convert PCI/endpoint/pci-test-function.txt " Changbin Du
2019-04-03 15:49 ` [PATCH v2 12/12] Documentation: PCI: convert PCI/endpoint/pci-test-howto.txt " Changbin Du
2019-04-03 16:58 ` Bjorn Helgaas [this message]
2019-04-03 19:23 ` [PATCH v2 00/12] Include linux PCI docs into Sphinx TOC tree Jonathan Corbet
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=20190403165858.GA67241@google.com \
--to=helgaas@kernel.org \
--cc=changbin.du@gmail.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 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.