From: Jonathan Corbet <corbet@lwn.net>
To: Rob Herring <robh@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/6] docs: writing-schema.md: convert from markdown to ReST
Date: Wed, 31 Jul 2019 14:48:16 -0600 [thread overview]
Message-ID: <20190731144816.71238678@lwn.net> (raw)
In-Reply-To: <20190731204500.GA6131@bogus>
On Wed, 31 Jul 2019 14:45:00 -0600
Rob Herring <robh@kernel.org> wrote:
> On Wed, Jul 31, 2019 at 05:08:49PM -0300, Mauro Carvalho Chehab wrote:
> > The documentation standard is ReST and not markdown.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > Acked-by: Rob Herring <robh@kernel.org>
> > ---
> > Documentation/devicetree/writing-schema.md | 130 -----------------
> > Documentation/devicetree/writing-schema.rst | 153 ++++++++++++++++++++
> > 2 files changed, 153 insertions(+), 130 deletions(-)
> > delete mode 100644 Documentation/devicetree/writing-schema.md
> > create mode 100644 Documentation/devicetree/writing-schema.rst
>
> Applied, thanks.
I've applied that to docs-next as well - your ack suggested to me that you
weren't intending to take it...
jon
next prev parent reply other threads:[~2019-07-31 20:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 20:08 [PATCH 0/6] ReST conversion patches not applied yet Mauro Carvalho Chehab
2019-07-31 20:08 ` [PATCH 1/6] docs: fix a couple of new broken references Mauro Carvalho Chehab
2019-07-31 20:21 ` Rob Herring
2019-07-31 20:36 ` Dave Kleikamp
2019-07-31 20:08 ` [PATCH 2/6] docs: writing-schema.md: convert from markdown to ReST Mauro Carvalho Chehab
2019-07-31 20:45 ` Rob Herring
2019-07-31 20:48 ` Jonathan Corbet [this message]
2019-07-31 21:30 ` Rob Herring
2019-07-31 20:08 ` [PATCH 3/6] spi: docs: convert to ReST and add it to the kABI bookset Mauro Carvalho Chehab
2019-07-31 20:08 ` [PATCH 4/6] docs: fs: cifs: convert to ReST and add to admin-guide book Mauro Carvalho Chehab
2019-07-31 20:08 ` [PATCH 5/6] docs: fs: convert porting to ReST Mauro Carvalho Chehab
2019-07-31 20:17 ` Jonathan Corbet
2019-07-31 20:22 ` Mauro Carvalho Chehab
2019-07-31 20:08 ` [PATCH 6/6] docs: w1: convert to ReST and add to the kAPI group of docs Mauro Carvalho Chehab
2019-07-31 20:17 ` [PATCH 0/6] ReST conversion patches not applied yet Jonathan Corbet
2019-07-31 20:20 ` Mark Brown
2019-07-31 20:26 ` Mauro Carvalho Chehab
2019-07-31 20:37 ` Mark Brown
2019-07-31 21:27 ` Mauro Carvalho Chehab
2019-07-31 21:55 ` Mark Brown
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=20190731144816.71238678@lwn.net \
--to=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=robh@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).