From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>,
Andrea Parri <andrea.parri@amarulasolutions.com>,
Nicholas Piggin <npiggin@gmail.com>,
linux-arch@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>,
Luc Maranget <luc.maranget@inria.fr>,
Alan Stern <stern@rowland.harvard.edu>,
Akira Yokosawa <akiyks@gmail.com>,
Will Deacon <will.deacon@arm.com>,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
Daniel Lustig <dlustig@nvidia.com>,
Jade Alglave <j.alglave@ucl.ac.uk>
Subject: Re: [PATCH 0/8] Prepare files under Documentation/*.txt to build with Sphinx
Date: Thu, 11 Apr 2019 12:37:22 -0600 [thread overview]
Message-ID: <20190411123722.67d8cbe6@lwn.net> (raw)
In-Reply-To: <cover.1554889999.git.mchehab+samsung@kernel.org>
On Wed, 10 Apr 2019 06:56:19 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> In the past, we did some efforts to ensure that almost all files under
> Documentation/*.txt could be built with Sphinx.
>
> Some regressions happened there (and some new files got added).
> Fix those files in order to allow them to be able to build with Sphinx.
>
> The changes on this series are trivial, adding the minimum stuff to allow
> building those files with sphinx-build with no warnings and to make the
> contents minimally consistent with other documentation files.
I've applied this set, thanks.
jon
next prev parent reply other threads:[~2019-04-11 18:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 9:56 [PATCH 0/8] Prepare files under Documentation/*.txt to build with Sphinx Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 1/8] docs: DMA-API-HOWTO: add a missing "=" Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 2/8] docs: atomic_bitops.txt: add a title for this document Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 3/8] docs: clearing-warn-once.txt: " Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 4/8] docs: ntb.txt: use Sphinx notation for the two ascii figures Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 5/8] docs: unaligned-memory-access.txt: use a lowercase title Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 6/8] docs: video-output.txt: convert it to ReST format Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 7/8] docs: ntb.txt: add blank lines to clean up some Sphinx warnings Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 8/8] docs: speculation.txt: mark example blocks as such Mauro Carvalho Chehab
2019-04-11 18:37 ` Jonathan Corbet [this message]
2019-04-12 10:21 ` [PATCH 0/8] Prepare files under Documentation/*.txt to build with Sphinx David Howells
2019-04-12 10:31 ` Markus Heiser
2019-04-12 12:19 ` David Howells
2019-04-12 12:34 ` Markus Heiser
2019-04-12 15:39 ` Jonathan Corbet
2019-04-12 16:45 ` Markus Heiser
2019-04-12 14:13 ` Jani Nikula
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=20190411123722.67d8cbe6@lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=npiggin@gmail.com \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.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).