Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Wed, 19 Apr 2023 17:28:21 -0700 you wrote:
> You can include an optional path after specifying the object name for the
> 'struct_ops register' subcommand.
>
> Since the commit 226bc6ae6405 ("Merge branch 'Transit between BPF TCP
> congestion controls.'") has been accepted, it is now possible to create a
> link for a struct_ops. This can be done by defining a struct_ops in
> SEC(".struct_ops.link") to make libbpf returns a real link. If we don't pin
> the links before leaving bpftool, they will disappear. To instruct bpftool
> to pin the links in a directory with the names of the maps, we need to
> provide the path of that directory.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpftool: Register struct_ops with a link.
https://git.kernel.org/bpf/bpf-next/c/0232b7889786
- [bpf-next,v3,2/2] bpftool: Update doc to explain struct_ops register subcommand.
https://git.kernel.org/bpf/bpf-next/c/45cea721ea36
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
