From: Joe Perches <joe@perches.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 07/10] docs: Add all txt files to documentation
Date: Tue, 09 Apr 2019 09:47:31 -0700 [thread overview]
Message-ID: <94a1b22362ad839b1c686f52aa4e16c171881ae6.camel@perches.com> (raw)
In-Reply-To: <d70a2426b9ec33d22c83c18a300efd4148e636aa.1554742526.git.mchehab+samsung@kernel.org>
On Mon, 2019-04-08 at 13:58 -0300, Mauro Carvalho Chehab wrote:
> Allow generating documentation for all files
Please update the MAINTAINERS F: patterns too.
$ git grep -P "Documentation/\w*\.txt" MAINTAINERS
MAINTAINERS:F: Documentation/dcdbas.txt
MAINTAINERS:F: Documentation/kobject.txt
MAINTAINERS:F: Documentation/hw_random.txt
MAINTAINERS:F: Documentation/hwspinlock.txt
MAINTAINERS:F: Documentation/intel_txt.txt
MAINTAINERS:F: Documentation/IPMI.txt
MAINTAINERS:F: Documentation/isa.txt
MAINTAINERS:F: Documentation/isapnp.txt
MAINTAINERS:F: Documentation/kprobes.txt
MAINTAINERS:F: Documentation/atomic_bitops.txt
MAINTAINERS:F: Documentation/atomic_t.txt
MAINTAINERS:F: Documentation/ldm.txt
MAINTAINERS:F: Documentation/padata.txt
MAINTAINERS:F: Documentation/switchtec.txt
MAINTAINERS:F: Documentation/pwm.txt
MAINTAINERS:F: Documentation/rtc.txt
MAINTAINERS:F: Documentation/remoteproc.txt
MAINTAINERS:F: Documentation/rpmsg.txt
MAINTAINERS:F: Documentation/rfkill.txt
MAINTAINERS:F: Documentation/svga.txt
MAINTAINERS:F: Documentation/sync_file.txt
MAINTAINERS:F: Documentation/tee.txt
MAINTAINERS:F: Documentation/vfio.txt
next prev parent reply other threads:[~2019-04-09 16:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 16:58 [PATCH 00/10] Add all documentation files to an html/pdf produced book Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 01/10] docs: DMA-API-HOWTO: add a missing "=" Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 02/10] docs: atomic_bitops.txt: add a title for this document Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 03/10] docs: clearing-warn-once.txt: " Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 04/10] docs: ntb.txt: use Sphinx notation for the two ascii figures Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 05/10] docs: unaligned-memory-access.txt: use a lowercase title Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 06/10] docs: video-output.txt: convert it to ReST format Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 07/10] docs: Add all txt files to documentation Mauro Carvalho Chehab
2019-04-09 16:47 ` Joe Perches [this message]
2019-04-08 16:58 ` [PATCH 08/10] docs: ntb.rst: add blank lines to clean up some Sphinx warnings Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 09/10] docs: speculation.rst: mark example blocks as such Mauro Carvalho Chehab
2019-04-08 16:58 ` [PATCH 10/10] docs: add plain text files to ReST output from subdirs Mauro Carvalho Chehab
2019-04-08 22:18 ` [PATCH 00/10] Add all documentation files to an html/pdf produced book Jonathan Corbet
2019-04-10 9:49 ` Mauro Carvalho Chehab
2019-04-11 18:49 ` Jonathan Corbet
2019-04-12 9:28 ` Mauro Carvalho Chehab
2019-04-13 0:30 ` 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=94a1b22362ad839b1c686f52aa4e16c171881ae6.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.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).