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, Atish Patra <atish.patra@wdc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Karsten Merker <merker@debian.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] docs: riscv: convert boot-image-header.txt to ReST
Date: Wed, 31 Jul 2019 13:02:24 -0600 [thread overview]
Message-ID: <20190731130224.1ebc92fa@lwn.net> (raw)
In-Reply-To: <1eaeb3fbb74de55af0b3f6d93ab40776dcbbb5c8.1564174903.git.mchehab+samsung@kernel.org>
On Fri, 26 Jul 2019 18:01:55 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> Convert this small file to ReST format by:
> - Using a proper markup for the document title;
> - marking a code block as such;
> - use tags for Author and date;
> - use tables for bit map fields.
>
> While here, fix a broken reference for a document with is
> planned but is not here yet.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Applied, thanks.
jon
next prev parent reply other threads:[~2019-07-31 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 11:47 [PATCH 0/7] Fix broken references to files under Documentation/* Mauro Carvalho Chehab
2019-07-26 19:55 ` Atish Patra
2019-07-26 20:13 ` Mauro Carvalho Chehab
2019-07-26 20:18 ` Atish Patra
2019-07-26 21:01 ` Mauro Carvalho Chehab
2019-07-26 22:16 ` Atish Patra
2019-07-26 21:01 ` [PATCH] docs: riscv: convert boot-image-header.txt to ReST Mauro Carvalho Chehab
2019-07-26 22:24 ` Atish Patra
2019-07-31 19:02 ` Jonathan Corbet [this message]
[not found] ` <CGME20190809101313eucas1p1363a5f60c06081bd9b2ef9b45248414f@eucas1p1.samsung.com>
2019-08-09 10:13 ` [PATCH 0/7] Fix broken references to files under Documentation/* Łukasz Stelmach
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=20190731130224.1ebc92fa@lwn.net \
--to=corbet@lwn.net \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=merker@debian.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.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).