From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
songliubraving@fb.com, yhs@fb.com, qmo@kernel.org
Subject: Re: [PATCHv4 bpf-next 0/3] bpf: tracing_multi link info support
Date: Wed, 01 Jul 2026 19:50:12 +0000 [thread overview]
Message-ID: <178293541264.1269008.13935548760043177318.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260629212208.895962-1-jolsa@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 29 Jun 2026 23:22:05 +0200 you wrote:
> hi,
> adding link info support for tracing_multi link.
>
> Adding the kernel support with related selftests and bpftool support
> to display the tracing_multi link info, the output looks like:
>
> # bpftool link
> ...
> 61: tracing_multi prog 167
> attach_type trace_fentry_multi btf_obj_id 1 count 3
> btf_id addr cookie func [module]
> 92598 ffffffff825017c4 10 bpf_fentry_test1
> 92600 ffffffff82503814 30 bpf_fentry_test2
> 92601 ffffffff82503824 20 bpf_fentry_test3
> pids test_progs(1540)
>
> [...]
Here is the summary with links:
- [PATCHv4,bpf-next,1/3] bpf: Add tracing_multi link info support
https://git.kernel.org/bpf/bpf-next/c/859055e07697
- [PATCHv4,bpf-next,2/3] selftests/bpf: Add tracing_multi link info tests
https://git.kernel.org/bpf/bpf-next/c/d36e4dd547bb
- [PATCHv4,bpf-next,3/3] bpftool: Add tracing_multi link info output
https://git.kernel.org/bpf/bpf-next/c/37c1e353c9fd
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:[~2026-07-01 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 21:22 [PATCHv4 bpf-next 0/3] bpf: tracing_multi link info support Jiri Olsa
2026-06-29 21:22 ` [PATCHv4 bpf-next 1/3] bpf: Add " Jiri Olsa
2026-06-29 21:22 ` [PATCHv4 bpf-next 2/3] selftests/bpf: Add tracing_multi link info tests Jiri Olsa
2026-06-29 21:34 ` sashiko-bot
2026-07-01 11:31 ` Jiri Olsa
2026-06-29 21:22 ` [PATCHv4 bpf-next 3/3] bpftool: Add tracing_multi link info output Jiri Olsa
2026-06-29 21:33 ` sashiko-bot
2026-07-01 11:31 ` Jiri Olsa
2026-07-01 19:43 ` Andrii Nakryiko
2026-07-01 19:50 ` 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=178293541264.1269008.13935548760043177318.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=jolsa@kernel.org \
--cc=martin.lau@linux.dev \
--cc=qmo@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