From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, mykolal@fb.com,
kernel-team@meta.com
Subject: Re: [PATCH bpf-next v2 1/2] libbpf: implement bpf_usdt_arg_size BPF function
Date: Wed, 26 Feb 2025 18:20:29 +0000 [thread overview]
Message-ID: <174059402950.801235.7236301825400438498.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250224235756.2612606-1-ihor.solodrai@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 24 Feb 2025 15:57:55 -0800 you wrote:
> Information about USDT argument size is implicitly stored in
> __bpf_usdt_arg_spec, but currently it's not accessbile to BPF programs
> that use USDT.
>
> Implement bpf_sdt_arg_size() that returns the size of an USDT argument
> in bytes.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] libbpf: implement bpf_usdt_arg_size BPF function
https://git.kernel.org/bpf/bpf-next/c/b62dff14402a
- [bpf-next,v2,2/2] selftests/bpf: test bpf_usdt_arg_size() function
https://git.kernel.org/bpf/bpf-next/c/0ba0ef012eba
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:[~2025-02-26 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 23:57 [PATCH bpf-next v2 1/2] libbpf: implement bpf_usdt_arg_size BPF function Ihor Solodrai
2025-02-24 23:57 ` [PATCH bpf-next v2 2/2] selftests/bpf: test bpf_usdt_arg_size() function Ihor Solodrai
2025-02-26 14:36 ` Jiri Olsa
2025-02-26 14:34 ` [PATCH bpf-next v2 1/2] libbpf: implement bpf_usdt_arg_size BPF function Jiri Olsa
2025-02-26 18:20 ` 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=174059402950.801235.7236301825400438498.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=ihor.solodrai@linux.dev \
--cc=kernel-team@meta.com \
--cc=mykolal@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 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.