From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com,
daniel@iogearbox.net, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/2] libbpf: support modules in set_attach_target() API
Date: Mon, 14 Dec 2020 15:50:06 +0000 [thread overview]
Message-ID: <160796100647.7023.1440666593259323373.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201211215825.3646154-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 11 Dec 2020 13:58:23 -0800 you wrote:
> Add support for finding BTF-based kernel attach targets (fentry/fexit
> functions, tp_btf tracepoints, etc) with programmatic
> bpf_program__set_attach_target() API. It is now as capable as libbpf's
> SEC()-based logic.
>
> Andrii Nakryiko (2):
> libbpf: support modules in bpf_program__set_attach_target() API
> selftests/bpf: add set_attach_target() API selftest for module target
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] libbpf: support modules in bpf_program__set_attach_target() API
https://git.kernel.org/bpf/bpf-next/c/fe62de310e2b
- [bpf-next,2/2] selftests/bpf: add set_attach_target() API selftest for module target
https://git.kernel.org/bpf/bpf-next/c/2e33f831fccd
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:[~2020-12-14 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 21:58 [PATCH bpf-next 0/2] libbpf: support modules in set_attach_target() API Andrii Nakryiko
2020-12-11 21:58 ` [PATCH bpf-next 1/2] libbpf: support modules in bpf_program__set_attach_target() API Andrii Nakryiko
2020-12-11 21:58 ` [PATCH bpf-next 2/2] selftests/bpf: add set_attach_target() API selftest for module target Andrii Nakryiko
2020-12-14 15: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=160796100647.7023.1440666593259323373.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).