From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: acme@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, linux-perf-users@vger.kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org, mingo@kernel.org,
namhyung@kernel.org, alexander.shishkin@linux.intel.com,
a.p.zijlstra@chello.nl, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, irogers@google.com
Subject: Re: [PATCHv5 bpf-next 0/1] perf tools: Fix prologue generation
Date: Fri, 24 Jun 2022 20:40:12 +0000 [thread overview]
Message-ID: <165610321291.32168.11018330141135892002.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220616202214.70359-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 16 Jun 2022 22:22:13 +0200 you wrote:
> hi,
> sending change we discussed some time ago [1] to get rid of
> some deprecated functions we use in perf prologue code.
>
> Despite the gloomy discussion I think the final code does
> not look that bad ;-)
>
> [...]
Here is the summary with links:
- [PATCHv5,bpf-next,1/1] perf tools: Rework prologue generation code
https://git.kernel.org/bpf/bpf-next/c/b168852eb8ef
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-06-24 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 20:22 [PATCHv5 bpf-next 0/1] perf tools: Fix prologue generation Jiri Olsa
2022-06-16 20:22 ` [PATCHv5 bpf-next 1/1] perf tools: Rework prologue generation code Jiri Olsa
2022-06-20 12:43 ` Daniel Borkmann
2022-08-01 17:44 ` Arnaldo Carvalho de Melo
2022-06-24 18:59 ` Arnaldo Carvalho de Melo
2022-06-24 20:40 ` patchwork-bot+netdevbpf [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=165610321291.32168.11018330141135892002.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=irogers@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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).