From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: doc: Correct title markers for asciidoctor
Date: Wed, 7 Mar 2018 10:26:24 -0300 [thread overview]
Message-ID: <20180307132624.GB3701@kernel.org> (raw)
In-Reply-To: <20180307105441.28512-1-tiwai@suse.de>
Em Wed, Mar 07, 2018 at 11:54:41AM +0100, Takashi Iwai escreveu:
> I've tested to process the perf man pages with asciidoctor that is
> picker than asciidoc, and it revealed minor syntax errors in some
> documents. Namely, the title markers aren't aligned with the previous
> line, hence asciidoctor didn't recognize as titles.
>
> This patch corrects these markers to be processed properly.
Thanks, applying.
- Arnaldo
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> ---
> tools/perf/Documentation/perf-data.txt | 2 +-
> tools/perf/Documentation/perf-ftrace.txt | 2 +-
> tools/perf/Documentation/perf-kallsyms.txt | 2 +-
> tools/perf/Documentation/perf-sched.txt | 2 +-
> tools/perf/Documentation/perf-script-perl.txt | 2 +-
> 5 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/tools/perf/Documentation/perf-data.txt b/tools/perf/Documentation/perf-data.txt
> index 90bb4aabe4f8..c87180764829 100644
> --- a/tools/perf/Documentation/perf-data.txt
> +++ b/tools/perf/Documentation/perf-data.txt
> @@ -1,5 +1,5 @@
> perf-data(1)
> -==============
> +============
>
> NAME
> ----
> diff --git a/tools/perf/Documentation/perf-ftrace.txt b/tools/perf/Documentation/perf-ftrace.txt
> index 721a447f046e..b80c84307dc9 100644
> --- a/tools/perf/Documentation/perf-ftrace.txt
> +++ b/tools/perf/Documentation/perf-ftrace.txt
> @@ -1,5 +1,5 @@
> perf-ftrace(1)
> -=============
> +==============
>
> NAME
> ----
> diff --git a/tools/perf/Documentation/perf-kallsyms.txt b/tools/perf/Documentation/perf-kallsyms.txt
> index 954ea9e21236..cdd421cd1c57 100644
> --- a/tools/perf/Documentation/perf-kallsyms.txt
> +++ b/tools/perf/Documentation/perf-kallsyms.txt
> @@ -1,5 +1,5 @@
> perf-kallsyms(1)
> -==============
> +================
>
> NAME
> ----
> diff --git a/tools/perf/Documentation/perf-sched.txt b/tools/perf/Documentation/perf-sched.txt
> index c7e50f263887..bb33601a823b 100644
> --- a/tools/perf/Documentation/perf-sched.txt
> +++ b/tools/perf/Documentation/perf-sched.txt
> @@ -1,5 +1,5 @@
> perf-sched(1)
> -==============
> +=============
>
> NAME
> ----
> diff --git a/tools/perf/Documentation/perf-script-perl.txt b/tools/perf/Documentation/perf-script-perl.txt
> index 142606c0ec9c..5a1f68122f50 100644
> --- a/tools/perf/Documentation/perf-script-perl.txt
> +++ b/tools/perf/Documentation/perf-script-perl.txt
> @@ -1,5 +1,5 @@
> perf-script-perl(1)
> -==================
> +===================
>
> NAME
> ----
> --
> 2.16.2
next prev parent reply other threads:[~2018-03-07 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 10:54 [PATCH] perf: doc: Correct title markers for asciidoctor Takashi Iwai
2018-03-07 13:26 ` Arnaldo Carvalho de Melo [this message]
2018-03-09 8:41 ` [tip:perf/core] perf tools: " tip-bot for Takashi Iwai
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=20180307132624.GB3701@kernel.org \
--to=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tiwai@suse.de \
/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).