All of lore.kernel.org
 help / color / mirror / Atom feed
From: Changbin Du <changbin.du@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Changbin Du <changbin.du@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/12] Include linux PCI docs into Sphinx TOC tree
Date: Wed, 3 Apr 2019 23:39:19 +0800	[thread overview]
Message-ID: <20190403153917.4r73hhzjp6anuyhj@mail.google.com> (raw)
In-Reply-To: <20190402180744.GD141706@google.com>

On Tue, Apr 02, 2019 at 01:07:44PM -0500, Bjorn Helgaas wrote:
> On Tue, Apr 02, 2019 at 11:08:54PM +0800, Changbin Du wrote:
> > On Mon, Apr 01, 2019 at 06:03:21PM -0500, Bjorn Helgaas wrote:
> > > On Sat, Mar 30, 2019 at 12:04:01AM +0800, Changbin Du wrote:
> > > > Changbin Du (12):
> > > >   Documentation: add Linux PCI to Sphinx TOC tree
> > > >   pci doc: convert PCI/pci.txt to rst format
> > > >   pci doc: convert PCI/PCIEBUS-HOWTO.txt to rst format
> > > >   pci doc: convert PCI/pci-iov-howto.txt to rst format
> > > >   pci doc: convert PCI/MSI-HOWTO.txt to rst format
> > > >   pci doc: convert PCI/acpi-info.txt to rst format
> > > >   pci doc: convert PCI/pci-error-recovery.txt to rst format
> > > >   pci doc: convert PCI/pcieaer-howto.txt to rst format
> > > >   pci doc: convert PCI/endpoint/pci-endpoint.txt to rst format
> > > >   pci doc: convert PCI/endpoint/pci-endpoint-cfs.txt to rst format
> > > >   pci doc: convert PCI/endpoint/pci-test-function.txt to rst format
> > > >   pci doc: convert PCI/endpoint/pci-test-howto.txt to rst format
> > > 
> > > Thanks for doing all this work!
> > > 
> > > Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> > > 
> > > There's not a real convention yet for subject lines in Documentation/,
> > > but I would propose:
> > > 
> > >   Documentation: PCI: Convert pci.txt to reST
> > >   Documentation: PCI: Convert endpoint/pci-endpoint.txt to reST
> > > 
> > > because that at least goes with some recent Documentation/PCI changes
> > > and it identifies "reST" as something other than a plain English word
> > > (RST or ReST would also work for me).
> > > 
> > I agree. I am just a little lazy to update all of them this time :)
> > Thanks for your ACK!
> 
> Well, I guess I'm too lazy to fix them all for you, so I personally
> wouldn't apply these.  But maybe Jonathan will be more accommodating.
>
ok, I will fix this serias since they do matter.

> Bjorn

-- 
Cheers,
Changbin Du

      reply	other threads:[~2019-04-03 15:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 16:04 [PATCH 00/12] Include linux PCI docs into Sphinx TOC tree Changbin Du
2019-03-29 16:04 ` [PATCH 01/12] Documentation: add Linux PCI to " Changbin Du
2019-03-29 16:04 ` [PATCH 02/12] pci doc: convert PCI/pci.txt to rst format Changbin Du
2019-03-29 16:04 ` [PATCH 03/12] pci doc: convert PCI/PCIEBUS-HOWTO.txt " Changbin Du
2019-03-29 16:04 ` [PATCH 04/12] pci doc: convert PCI/pci-iov-howto.txt " Changbin Du
2019-03-29 16:04 ` [PATCH 05/12] pci doc: convert PCI/MSI-HOWTO.txt " Changbin Du
2019-03-30  4:00   ` Matthew Wilcox
2019-03-31  5:18     ` Changbin Du
2019-03-31 15:33   ` Changbin Du
2019-03-29 16:04 ` [PATCH 06/12] pci doc: convert PCI/acpi-info.txt " Changbin Du
2019-03-29 16:04 ` [PATCH 07/12] pci doc: convert PCI/pci-error-recovery.txt " Changbin Du
2019-03-29 16:04 ` [PATCH 08/12] pci doc: convert PCI/pcieaer-howto.txt " Changbin Du
2019-03-29 16:04 ` [PATCH 09/12] pci doc: convert PCI/endpoint/pci-endpoint.txt " Changbin Du
2019-03-29 16:04 ` [PATCH 10/12] pci doc: convert PCI/endpoint/pci-endpoint-cfs.txt " Changbin Du
2019-03-29 16:04 ` [PATCH 11/12] pci doc: convert PCI/endpoint/pci-test-function.txt " Changbin Du
2019-03-29 16:04 ` [PATCH 12/12] pci doc: convert PCI/endpoint/pci-test-howto.txt " Changbin Du
2019-04-01 23:03 ` [PATCH 00/12] Include linux PCI docs into Sphinx TOC tree Bjorn Helgaas
2019-04-02 15:08   ` Changbin Du
2019-04-02 18:07     ` Bjorn Helgaas
2019-04-03 15:39       ` Changbin Du [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=20190403153917.4r73hhzjp6anuyhj@mail.google.com \
    --to=changbin.du@gmail.com \
    --cc=corbet@lwn.net \
    --cc=helgaas@kernel.org \
    --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.