From: patchwork-bot+netdevbpf@kernel.org
To: Hao Luo <haoluo@google.com>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
jolsa@kernel.org, kpsingh@kernel.org, john.fastabend@gmail.com,
sdf@google.com, yosryahmed@google.com
Subject: Re: [PATCH bpf-next v2 1/2] libbpf: Allows disabling auto attach
Date: Wed, 17 Aug 2022 16:50:15 +0000 [thread overview]
Message-ID: <166075501543.29308.8178577555614859134.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220816234012.910255-1-haoluo@google.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 16 Aug 2022 16:40:11 -0700 you wrote:
> Adds libbpf APIs for disabling auto-attach for individual functions.
> This is motivated by the use case of cgroup iter [1]. Some iter
> types require their parameters to be non-zero, therefore applying
> auto-attach on them will fail. With these two new APIs, users who
> want to use auto-attach and these types of iters can disable
> auto-attach on the program and perform manual attach.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] libbpf: Allows disabling auto attach
https://git.kernel.org/bpf/bpf-next/c/43cb8cbadffa
- [bpf-next,v2,2/2] selftests/bpf: Tests libbpf autoattach APIs
https://git.kernel.org/bpf/bpf-next/c/738a2f2f9130
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:[~2022-08-17 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 23:40 [PATCH bpf-next v2 1/2] libbpf: Allows disabling auto attach Hao Luo
2022-08-16 23:40 ` [PATCH bpf-next v2 2/2] selftests/bpf: Tests libbpf autoattach APIs Hao Luo
2022-08-17 16: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=166075501543.29308.8178577555614859134.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
--cc=yosryahmed@google.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