From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
linux-mtd@lists.infradead.org, tboot-devel@lists.sourceforge.net,
Emese Revfy <re.emese@gmail.com>, Li Zefan <lizefan@huawei.com>,
Ning Sun <ning.sun@intel.com>, Kees Cook <keescook@chromium.org>,
Tejun Heo <tj@kernel.org>,
linux-crypto@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
cgroups@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
Johann
Subject: [PATCH 00/31] Standardize doc formats - part 1
Date: Thu, 18 May 2017 22:22:05 -0300 [thread overview]
Message-ID: <cover.1495156488.git.mchehab@s-opensource.com> (raw)
Each document under Documentation/*.txt has its own format.
Some follow markup notations, some don't even have a title!
In order to try to get some order on it, change the document
style to the standard we're adopting after the adoption of
ReStructured Text.
The documents touched on this series now build fine with
Sphinx, if renamed to *.rst extension.
The main goal with this is to teach people by example about
what format is expected on newer documents. It also helps
to add those files to Kernel books.
In order to make things more palatable, I'm spliting the
conversion into three parts.
This is part 1.
Mauro Carvalho Chehab (31):
bcache.txt: standardize document format
bt8xxgpio.txt: standardize document format
btmrvl.txt: standardize document format
bus-virt-phys-mapping.txt: standardize document format
cachetlb.txt: standardize document format
cgroup-v2.txt: standardize document format
circular-buffers.txt: standardize document format
clk.txt: standardize document format
cpu-load: standardize document format
cputopology.txt: standardize document format
crc32.txt: standardize document format
dcdbas.txt: standardize document format
digsig.txt: standardize document format
DMA-API.txt: standardize document format
DMA-API-HOWTO.txt: standardize document format
DMA-attributes.txt: standardize document format
DMA-ISA-LPC.txt: standardize document format
debugging-via-ohci1394.txt: standardize document format
efi-stub.txt: standardize document format
eisa.txt: standardize document format
flexible-arrays.txt: standardize document format
futex-requeue-pi.txt: standardize document format
gcc-plugins.txt: standardize document format
highuid.txt: standardize document format
hw_random.txt: standardize document format
hwspinlock.txt: standardize document format
intel_txt.txt: standardize document format
Intel-IOMMU.txt: standardize document format
io-mapping.txt: standardize document format
io_ordering.txt: standardize document format
iostats.txt: standardize document format
Documentation/DMA-API-HOWTO.txt | 159 +++++----
Documentation/DMA-API.txt | 575 ++++++++++++++++++-------------
Documentation/DMA-ISA-LPC.txt | 71 ++--
Documentation/DMA-attributes.txt | 15 +-
Documentation/Intel-IOMMU.txt | 36 +-
Documentation/bcache.txt | 200 ++++++-----
Documentation/bt8xxgpio.txt | 19 +-
Documentation/btmrvl.txt | 64 ++--
Documentation/bus-virt-phys-mapping.txt | 63 ++--
Documentation/cachetlb.txt | 92 ++---
Documentation/cgroup-v2.txt | 449 ++++++++++++------------
Documentation/circular-buffers.txt | 51 ++-
Documentation/clk.txt | 189 +++++-----
Documentation/cpu-load.txt | 117 +++----
Documentation/cputopology.txt | 35 +-
Documentation/crc32.txt | 75 ++--
Documentation/dcdbas.txt | 24 +-
Documentation/debugging-via-ohci1394.txt | 21 +-
Documentation/digsig.txt | 124 +++----
Documentation/efi-stub.txt | 25 +-
Documentation/eisa.txt | 260 +++++++-------
Documentation/flexible-arrays.txt | 24 +-
Documentation/futex-requeue-pi.txt | 83 ++---
Documentation/gcc-plugins.txt | 58 ++--
Documentation/highuid.txt | 46 +--
Documentation/hw_random.txt | 158 +++++----
Documentation/hwspinlock.txt | 527 ++++++++++++++++------------
Documentation/intel_txt.txt | 63 ++--
Documentation/io-mapping.txt | 67 ++--
Documentation/io_ordering.txt | 61 ++--
Documentation/iostats.txt | 40 ++-
31 files changed, 2101 insertions(+), 1690 deletions(-)
--
2.9.4
next reply other threads:[~2017-05-19 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 1:22 Mauro Carvalho Chehab [this message]
2017-05-19 1:22 ` [PATCH 06/31] cgroup-v2.txt: standardize document format Mauro Carvalho Chehab
[not found] ` <1f0804f2263073287d2a106c12f88f295a30cec5.1495156488.git.mchehab-JsYNTwtnfakRB7SZvlqPiA@public.gmane.org>
2017-05-19 14:59 ` Tejun Heo
2017-06-17 15:18 ` Mauro Carvalho Chehab
2017-06-18 10:46 ` Tejun Heo
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=cover.1495156488.git.mchehab@s-opensource.com \
--to=mchehab@s-opensource.com \
--cc=boris.brezillon@free-electrons.com \
--cc=cgroups@vger.kernel.org \
--cc=computersforpeace@gmail.com \
--cc=corbet@lwn.net \
--cc=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=keescook@chromium.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lizefan@huawei.com \
--cc=marek.vasut@gmail.com \
--cc=mchehab@infradead.org \
--cc=mingo@redhat.com \
--cc=ning.sun@intel.com \
--cc=re.emese@gmail.com \
--cc=richard@nod.at \
--cc=tboot-devel@lists.sourceforge.net \
--cc=tj@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).