linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Changbin Du <changbin.du@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	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 13:23:05 -0600	[thread overview]
Message-ID: <20190403132305.41e6e185@lwn.net> (raw)
In-Reply-To: <20190403154955.12096-1-changbin.du@gmail.com>

On Wed,  3 Apr 2019 23:49:43 +0800
Changbin Du <changbin.du@gmail.com> wrote:

> 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!

So I have the same comment that I had with regard to the ACPI set: I would
really rather not clutter the top level of the doc tree with this.  In
this case the resolution is a lot simpler, though: everything here seems
suitable for the driver API guide.  Could you please redo the patch set to
place the docs there?

Reflecting Bjorn's comment on the title lines and adding his ack would be
a nice touch while you're at it.

Thanks for doing this work - this one's almost there, I think.

jon

      parent reply	other threads:[~2019-04-03 19:23 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 ` [PATCH v2 00/12] Include linux PCI docs into Sphinx TOC tree Bjorn Helgaas
2019-04-03 19:23 ` Jonathan Corbet [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=20190403132305.41e6e185@lwn.net \
    --to=corbet@lwn.net \
    --cc=bhelgaas@google.com \
    --cc=changbin.du@gmail.com \
    --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).