From: Steven Rostedt <rostedt@goodmis.org>
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, Jonathan Corbet <corbet@lwn.net>,
Ingo Molnar <mingo@redhat.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
James Morris <james.morris@microsoft.com>,
Xiongwei Song <sxwjean@me.com>,
Changbin Du <changbin.du@intel.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>
Subject: Re: [PATCH 9/9] docs: histogram.txt: convert it to ReST file format
Date: Tue, 26 Jun 2018 10:20:30 -0400 [thread overview]
Message-ID: <20180626102030.69bf840a@gandalf.local.home> (raw)
In-Reply-To: <4e8df7559e48b4b90bca73cf08d4e01497a39066.1530005114.git.mchehab+samsung@kernel.org>
On Tue, 26 Jun 2018 06:49:11 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> Despite being mentioned at Documentation/trace/ftrace.rst as a
> rst file, this file was still a text one, with several issues.
>
> Convert it to ReST and add it to the trace index:
> - Mark the document title as such;
> - Identify and indent the literal blocks;
> - Use the proper markups for table.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> ---
> Documentation/trace/events.rst | 2 +-
> .../trace/{histogram.txt => histogram.rst} | 1242 +++++++++--------
> Documentation/trace/index.rst | 1 +
> kernel/trace/Kconfig | 2 +-
> 4 files changed, 627 insertions(+), 620 deletions(-)
> rename Documentation/trace/{histogram.txt => histogram.rst} (73%)
>
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2018-06-26 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 9:49 [PATCH 0/9] Fix references for some missing documentation files Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 1/9] scripts/documentation-file-ref-check: remove some false positives Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 2/9] scripts/documentation-file-ref-check: ignore sched-pelt false positive Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 3/9] docs: zh_CN: fix location of oops-tracing.txt Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 4/9] devicectree: bindings: fix location of leds common file Mauro Carvalho Chehab
2018-06-26 14:38 ` Pavel Machek
2018-06-26 19:41 ` Jacek Anaszewski
2018-06-26 9:49 ` [PATCH 5/9] MAINTAINERS: fix location of ina2xx.txt device tree file Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 6/9] gpio.h: fix location of gpio legacy documentation Mauro Carvalho Chehab
2018-06-29 12:36 ` Linus Walleij
2018-06-26 9:49 ` [PATCH 7/9] networking: e100.rst: Get rid of Sphinx warnings Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 8/9] networking: e1000.rst: " Mauro Carvalho Chehab
2018-06-26 9:49 ` [PATCH 9/9] docs: histogram.txt: convert it to ReST file format Mauro Carvalho Chehab
2018-06-26 14:20 ` Steven Rostedt [this message]
2018-07-02 17:27 ` [PATCH 0/9] Fix references for some missing documentation files Jonathan Corbet
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=20180626102030.69bf840a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=changbin.du@intel.com \
--cc=corbet@lwn.net \
--cc=james.morris@microsoft.com \
--cc=joel@joelfernandes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=sxwjean@me.com \
--cc=tom.zanussi@linux.intel.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).