From: Ian Rogers <irogers@google.com>
To: Michael Petlan <mpetlan@redhat.com>
Cc: linux-perf-users@vger.kernel.org, acme@redhat.com, jolsa@kernel.org
Subject: Re: [PATCH 1/2] perf docs: Add perf-iostat link to manpages
Date: Tue, 5 Apr 2022 13:53:59 -0700 [thread overview]
Message-ID: <CAP-5=fVUs0rtEWsym4Sw7t83COvdOUFqGYi30_qX4zA=TMzJog@mail.gmail.com> (raw)
In-Reply-To: <20220404221541.30312-1-mpetlan@redhat.com>
On Mon, Apr 4, 2022 at 3:59 PM Michael Petlan <mpetlan@redhat.com> wrote:
>
> Signed-off-by: Michael Petlan <mpetlan@redhat.com>
Acked-by: Ian Rogers <irogers@google.com>
Thanks,
Ian
> ---
> tools/perf/Documentation/perf.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/Documentation/perf.txt b/tools/perf/Documentation/perf.txt
> index 9c330cdfa973..71ebdf8125de 100644
> --- a/tools/perf/Documentation/perf.txt
> +++ b/tools/perf/Documentation/perf.txt
> @@ -83,7 +83,7 @@ linkperf:perf-buildid-list[1], linkperf:perf-c2c[1],
> linkperf:perf-config[1], linkperf:perf-data[1], linkperf:perf-diff[1],
> linkperf:perf-evlist[1], linkperf:perf-ftrace[1],
> linkperf:perf-help[1], linkperf:perf-inject[1],
> -linkperf:perf-intel-pt[1], linkperf:perf-kallsyms[1],
> +linkperf:perf-intel-pt[1], linkperf:perf-iostat[1], linkperf:perf-kallsyms[1],
> linkperf:perf-kmem[1], linkperf:perf-kvm[1], linkperf:perf-lock[1],
> linkperf:perf-mem[1], linkperf:perf-probe[1], linkperf:perf-sched[1],
> linkperf:perf-script[1], linkperf:perf-test[1],
> --
> 2.18.4
>
next prev parent reply other threads:[~2022-04-05 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 22:15 [PATCH 1/2] perf docs: Add perf-iostat link to manpages Michael Petlan
2022-04-04 22:15 ` [PATCH 2/2] perf: Add external commands to list-cmds Michael Petlan
2022-04-05 20:54 ` Ian Rogers
2022-04-09 15:38 ` Arnaldo Carvalho de Melo
2022-04-05 20:53 ` Ian Rogers [this message]
2022-04-09 15:39 ` [PATCH 1/2] perf docs: Add perf-iostat link to manpages Arnaldo Carvalho de Melo
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='CAP-5=fVUs0rtEWsym4Sw7t83COvdOUFqGYi30_qX4zA=TMzJog@mail.gmail.com' \
--to=irogers@google.com \
--cc=acme@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.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).