From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Sandipan Das <sandipan.das@amd.com>
Cc: Ian Rogers <irogers@google.com>,
Kevin Nomura <nomurak@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Jiri Olsa <jolsa@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Alexey Bayduraev <alexey.v.bayduraev@linux.intel.com>,
Like Xu <likexu@tencent.com>, German Gomez <german.gomez@arm.com>,
Jin Yao <yao.jin@linux.intel.com>,
Kan Liang <kan.liang@linux.intel.com>, Alyssa Ross <hi@alyssa.is>,
Zhengjun Xing <zhengjun.xing@linux.intel.com>,
Joshua Martinez <joshuamart@google.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf docs: Correct typo of event_sources
Date: Fri, 3 Jun 2022 21:16:14 +0200 [thread overview]
Message-ID: <Yppd/rUoWN7na+Iz@kernel.org> (raw)
In-Reply-To: <13ddd896-d7a6-3539-2dcf-7ffe4f1a2569@amd.com>
Em Fri, Jun 03, 2022 at 11:30:00AM +0530, Sandipan Das escreveu:
>
> On 6/3/2022 10:27 AM, Ian Rogers wrote:
> > The sysfs directory is called event_source.
> >
> > Reported-by: Kevin Nomura <nomurak@google.com>
> > Signed-off-by: Ian Rogers <irogers@google.com>
> > ---
> > tools/perf/Documentation/perf-record.txt | 2 +-
> > tools/perf/Documentation/perf-stat.txt | 2 +-
> > tools/perf/Documentation/perf-top.txt | 2 +-
> > 3 files changed, 3 insertions(+), 3 deletions(-)
> >
> > [...]
>
> Thanks for fixing these.
>
> Reviewed-by: Sandipan Das <sandipan.das@amd.com>
Thanks, applied.
- Arnaldo
prev parent reply other threads:[~2022-06-03 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 4:57 [PATCH] perf docs: Correct typo of event_sources Ian Rogers
2022-06-03 6:00 ` Sandipan Das
2022-06-03 19:16 ` Arnaldo Carvalho de Melo [this message]
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=Yppd/rUoWN7na+Iz@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.v.bayduraev@linux.intel.com \
--cc=german.gomez@arm.com \
--cc=hi@alyssa.is \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=joshuamart@google.com \
--cc=kan.liang@linux.intel.com \
--cc=likexu@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nomurak@google.com \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=yao.jin@linux.intel.com \
--cc=zhengjun.xing@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.