From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Song Liu <song@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ming Wang <wangming01@loongson.cn>,
Ravi Bangoria <ravi.bangoria@amd.com>,
Huacai Chen <chenhuacai@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH v1] perf env: Avoid recursively taking env->bpf_progs.lock
Date: Wed, 3 Jan 2024 17:55:30 -0300 [thread overview]
Message-ID: <ZZXJwsYlGxYoQOeP@kernel.org> (raw)
In-Reply-To: <CAPhsuW6EZ-FoZFbCuxs7gAa0OaQGw0zMLDaeEsNoU31vjXijnQ@mail.gmail.com>
Em Wed, Jan 03, 2024 at 09:40:26AM -0800, Song Liu escreveu:
> On Wed, Jan 3, 2024 at 8:27 AM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > Applied, with that minor patch reduction hunk and this:
> > Fixes: f8dfeae009effc0b ("perf bpf: Show more BPF program info in print_bpf_prog_info()")
> > Song, can I have your Acked-by?
> LGTM. Thanks for the fix!
> Acked-by: Song Liu <song@kernel.org>
Thanks! Added to the cset.
- Arnaldo
next prev parent reply other threads:[~2024-01-03 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 1:46 [PATCH v1] perf env: Avoid recursively taking env->bpf_progs.lock Ian Rogers
2024-01-03 3:00 ` Ian Rogers
2024-01-03 16:27 ` Arnaldo Carvalho de Melo
2024-01-03 17:40 ` Song Liu
2024-01-03 20:55 ` Arnaldo Carvalho de Melo [this message]
2024-01-03 9:25 ` Jiri Olsa
2024-01-03 16:09 ` Arnaldo Carvalho de Melo
2024-01-03 16:24 ` Ian Rogers
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=ZZXJwsYlGxYoQOeP@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=chenhuacai@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kprateek.nayak@amd.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=ravi.bangoria@amd.com \
--cc=song@kernel.org \
--cc=wangming01@loongson.cn \
/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).