From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Masanari Iida <standby24x7@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH] perf bpf: Fix a typo in bpf_counter_cgroup.c
Date: Sun, 6 Feb 2022 08:49:09 -0300 [thread overview]
Message-ID: <Yf+1tRRYT9W8qgqO@kernel.org> (raw)
In-Reply-To: <CAM9d7cj0dQvoio-T0yNZzo+AGGDxCFtRWuDxBunFEkipWtDxZA@mail.gmail.com>
Em Tue, Dec 28, 2021 at 10:25:08AM -0800, Namhyung Kim escreveu:
> Hello,
>
> On Fri, Dec 24, 2021 at 4:57 PM Masanari Iida <standby24x7@gmail.com> wrote:
> >
> > This patch fixes a spelling typo in error message.
> >
> > Signed-off-by: Masanari Iida <standby24x7@gmail.com>
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
>
> Thanks,
> Namhyung
Thanks, applied.
- Arnaldo
>
> > ---
> > tools/perf/util/bpf_counter_cgroup.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/util/bpf_counter_cgroup.c b/tools/perf/util/bpf_counter_cgroup.c
> > index cbc6c2bca488..fea5f2ca03f6 100644
> > --- a/tools/perf/util/bpf_counter_cgroup.c
> > +++ b/tools/perf/util/bpf_counter_cgroup.c
> > @@ -266,7 +266,7 @@ static int bperf_cgrp__read(struct evsel *evsel)
> > idx = evsel->core.idx;
> > err = bpf_map_lookup_elem(reading_map_fd, &idx, values);
> > if (err) {
> > - pr_err("bpf map lookup falied: idx=%u, event=%s, cgrp=%s\n",
> > + pr_err("bpf map lookup failed: idx=%u, event=%s, cgrp=%s\n",
> > idx, evsel__name(evsel), evsel->cgrp->name);
> > goto out;
> > }
> > --
> > 2.25.0
> >
--
- Arnaldo
prev parent reply other threads:[~2022-02-06 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 0:55 [PATCH] perf bpf: Fix a typo in bpf_counter_cgroup.c Masanari Iida
2021-12-28 18:25 ` Namhyung Kim
2022-02-06 11:49 ` 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=Yf+1tRRYT9W8qgqO@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.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=peterz@infradead.org \
--cc=standby24x7@gmail.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).