From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Keith Busch <keith.busch@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH v1 29/31] docs: nvdimm: convert to ReST
Date: Wed, 12 Jun 2019 17:41:19 -0300 [thread overview]
Message-ID: <20190612174119.7c0d94bd@coco.lan> (raw)
In-Reply-To: <CAPcyv4g08r6bK_SyTjzKFRM7=wpTQLdmHqRSGh7r-e9YD4tq5Q@mail.gmail.com>
Em Wed, 12 Jun 2019 12:04:12 -0700
Dan Williams <dan.j.williams@intel.com> escreveu:
> Hi Mauro,
>
> On Wed, Jun 12, 2019 at 11:38 AM Mauro Carvalho Chehab
> <mchehab+samsung@kernel.org> wrote:
> >
> > Rename the mtd documentation files to ReST, add an
>
> s/mtd/nvdimm/
Sorry, cut and paste issue :-)
>
> > index for them and adjust in order to produce a nice html
> > output via the Sphinx build system.
> >
> > At its new index.rst, let's add a :orphan: while this is not linked to
> > the main index.rst file, in order to avoid build warnings.
>
> Looks ok, but I was not able to apply this one in isolation to give it
> a try. Am I missing some pre-reqs compared to v5.2-rc4?
I wrote the patch before v5.2-rc1, but, as this series touches a lot
of stuff, it was rebased against today's linux-next (next-20190612).
I didn't notice an conflict on this specific file during the rebases
though.
There is a simple patch applied on linux-next after v5.2-rc4:
commit 3d9cf48b2ca257f1a249b347236098c3cf9d54f1
Author: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com>
Date: Thu May 9 15:40:49 2019 +0800
Documentation: nvdimm: Fix typo
Remove the extra 'we '.
Signed-off-by: Shiyang Ruan <ruansy.fnst@cn.fujitsu.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Could this be the cause of the issue you're noticing when
trying to apply it?
As this is signed-off by Jon, I suspect it went via docs-next.
Thanks,
Mauro
next prev parent reply other threads:[~2019-06-12 20:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 18:38 [PATCH v1 00/31] Convert files to ReST - part 2 Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 01/31] docs: connector: convert to ReST and rename to connector.rst Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 02/31] docs: lcd-panel-cgram.txt: convert docs to ReST and rename to *.rst Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 03/31] docs: lp855x-driver.txt: convert to ReST and move to kernel-api Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 04/31] docs: m68k: convert docs to ReST and rename to *.rst Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 05/31] docs: cma/debugfs.txt: " Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 06/31] docs: console.txt: " Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 07/31] docs: pti_intel_mid.txt: convert it to pti_intel_mid.rst Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 08/31] docs: early-userspace: convert docs to ReST and rename to *.rst Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 09/31] docs: driver-model: " Mauro Carvalho Chehab
2019-06-12 20:21 ` Jeff Kirsher
2019-06-12 18:38 ` [PATCH v1 11/31] docs: memory-devices: convert ti-emif.txt to ReST Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 12/31] docs: xen-tpmfront.txt: convert it to .rst Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 13/31] docs: bus-devices: ti-gpmc.rst: convert it to ReST Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 14/31] docs: nvmem: convert docs to ReST and rename to *.rst Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 15/31] docs: phy: convert samsung-usb2.txt to ReST format Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 16/31] docs: rbtree.txt: fix Sphinx build warnings Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 17/31] docs: DMA-API-HOWTO.txt: fix an unmarked code block Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 18/31] docs: accounting: convert to ReST Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 19/31] docs: fmc: " Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 20/31] docs: hid: " Mauro Carvalho Chehab
2019-06-13 8:08 ` Benjamin Tissoires
2019-06-13 9:52 ` Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 21/31] docs: ia64: " Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 22/31] docs: leds: " Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 23/31] docs: laptops: " Mauro Carvalho Chehab
2019-06-12 20:19 ` Andy Shevchenko
2019-06-12 18:38 ` [PATCH v1 24/31] docs: iio: " Mauro Carvalho Chehab
2019-06-16 13:47 ` Jonathan Cameron
2019-06-12 18:38 ` [PATCH v1 25/31] docs: namespaces: " Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 26/31] docs: nfc: " Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 27/31] docs: md: " Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 28/31] docs: mtd: " Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 29/31] docs: nvdimm: " Mauro Carvalho Chehab
2019-06-12 19:04 ` Dan Williams
2019-06-12 20:41 ` Mauro Carvalho Chehab [this message]
2019-06-12 18:38 ` [PATCH v1 30/31] docs: xtensa: " Mauro Carvalho Chehab
2019-06-12 18:38 ` [PATCH v1 31/31] docs: mmc: " Mauro Carvalho Chehab
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=20190612174119.7c0d94bd@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mchehab@infradead.org \
--cc=vishal.l.verma@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).