From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
kvm@vger.kernel.org,
"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
linux-efi@vger.kernel.org,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Will Deacon" <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
"Mauro Carvalho Chehab" <mchehab@infradead.org>,
"Harry Wei" <harryxiyou@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Shi" <alex.shi@linux.alibaba.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 02/28] docs: arm64: convert docs to ReST and rename to .rst
Date: Fri, 14 Jun 2019 14:10:41 -0600 [thread overview]
Message-ID: <20190614141041.335a76e5@lwn.net> (raw)
In-Reply-To: <8320e8e871660bf9fc426bc688f4808a1a7aa031.1560361364.git.mchehab+samsung@kernel.org>
On Wed, 12 Jun 2019 14:52:38 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> The documentation is in a format that is very close to ReST format.
>
> The conversion is actually:
> - add blank lines in order to identify paragraphs;
> - fixing tables markups;
> - adding some lists markups;
> - marking literal blocks;
> - adjust some title markups.
>
> 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.
This one doesn't apply to docs-next, since there's a bunch of stuff in
linux-next that I don't have. I'd suggest that it either go by way of an
ARM tree or send it my way again after the ARM changes go upstream.
Thanks,
jon
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-14 20:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1560361364.git.mchehab+samsung@kernel.org>
2019-06-12 17:52 ` [PATCH v4 02/28] docs: arm64: convert docs to ReST and rename to .rst Mauro Carvalho Chehab
2019-06-14 20:10 ` Jonathan Corbet [this message]
2019-06-14 20:34 ` Jonathan Corbet
2019-06-12 17:52 ` [PATCH v4 13/28] docs: kdump: convert docs to ReST and rename to *.rst Mauro Carvalho Chehab
2019-06-12 17:52 ` [PATCH v4 19/28] docs: powerpc: " Mauro Carvalho Chehab
2019-06-14 20:36 ` Jonathan Corbet
2019-06-14 21:30 ` Bjorn Helgaas
2019-06-18 12:39 ` Michael Ellerman
2019-06-12 17:53 ` [PATCH v4 26/28] docs: xilinx: convert eemi.txt to eemi.rst Mauro Carvalho Chehab
[not found] ` <fac44e1fbab5ea755a93601a4fdfa34fcc57ae9e.1560361364.git.mchehab+samsung@kernel.org>
2019-06-13 0:25 ` [PATCH v4 18/28] docs: convert docs to ReST and rename to *.rst Srivatsa S. Bhat
2019-06-13 9:58 ` Mauro Carvalho Chehab
[not found] ` <72d1f8f360d395958dd0b49165fc51b58801f57e.1560420621.git.mchehab+samsung@kernel.org>
2019-06-14 20:36 ` [PATCH v5] docs: power: " Jonathan Corbet
2019-06-14 21:14 ` Bjorn Helgaas
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=20190614141041.335a76e5@lwn.net \
--to=corbet@lwn.net \
--cc=alex.shi@linux.alibaba.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=harryxiyou@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--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).