Re: [PATCH v2 bpf-next 0/3] Add target-less tracing SEC() definitions

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Thu, 28 Apr 2022 11:53:46 -0700 you wrote:
> Allow specifying "target-less" SEC() definitions for tracing BPF programs,
> both non-BTF-backed (kprobes, tracepoints, raw tracepoints) and BTF-backed
> (fentry/fexit, iter, lsm, etc).
> 
> There are various situations where attach target cannot be known at
> compilation time, so libbpf's insistence on specifying something leads to
> users having to add random test like SEC("kprobe/whatever") and then
> specifying correct target at runtime using APIs like
> bpf_program__attach_kprobe().
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next,1/3] libbpf: allow "incomplete" basic tracing SEC() definitions
    https://git.kernel.org/bpf/bpf-next/c/9af8efc45eb1
  - [v2,bpf-next,2/3] libbpf: support target-less SEC() definitions for BTF-backed programs
    https://git.kernel.org/bpf/bpf-next/c/cc7d8f2c8ecc
  - [v2,bpf-next,3/3] selftests/bpf: use target-less SEC() definitions in various tests
    https://git.kernel.org/bpf/bpf-next/c/32c03c4954a0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html