From: patchwork-bot+netdevbpf@kernel.org
To: Kui-Feng Lee <thinker.li@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
song@kernel.org, kernel-team@meta.com, andrii@kernel.org,
yhs@meta.com, quentin@isovalent.com, kuifeng@meta.com
Subject: Re: [PATCH bpf-next v3 1/2] bpftool: Register struct_ops with a link.
Date: Fri, 21 Apr 2023 18:20:19 +0000 [thread overview]
Message-ID: <168210121978.28314.15375823140972222895.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230420002822.345222-1-kuifeng@meta.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
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
prev parent reply other threads:[~2023-04-21 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 0:28 [PATCH bpf-next v3 1/2] bpftool: Register struct_ops with a link Kui-Feng Lee
2023-04-20 0:28 ` [PATCH bpf-next v3 2/2] bpftool: Update doc to explain struct_ops register subcommand Kui-Feng Lee
2023-04-20 0:42 ` Quentin Monnet
2023-04-20 0:42 ` [PATCH bpf-next v3 1/2] bpftool: Register struct_ops with a link Quentin Monnet
2023-04-21 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=168210121978.28314.15375823140972222895.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=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=quentin@isovalent.com \
--cc=song@kernel.org \
--cc=thinker.li@gmail.com \
--cc=yhs@meta.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