From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/4] libbpf: allow to opt-out from BPF map creation
Date: Fri, 29 Apr 2022 03:20:11 +0000 [thread overview]
Message-ID: <165120241196.28026.9393761391052858735.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220428041523.4089853-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 27 Apr 2022 21:15:19 -0700 you wrote:
> Add bpf_map__set_autocreate() API which is a BPF map counterpart of
> bpf_program__set_autoload() and serves similar goal of allowing to build more
> flexible CO-RE applications. See patch #3 for example scenarios in which the
> need for such API came up previously.
>
> Patch #1 is a follow-up patch to previous patch set adding verifier log fixup
> logic, making sure bpf_core_format_spec()'s return result is used for
> something useful.
>
> [...]
Here is the summary with links:
- [bpf-next,1/4] libbpf: append "..." in fixed up log if CO-RE spec is truncated
https://git.kernel.org/bpf/bpf-next/c/b198881d4b4c
- [bpf-next,2/4] libbpf: use libbpf_mem_ensure() when allocating new map
https://git.kernel.org/bpf/bpf-next/c/69721203b1f3
- [bpf-next,3/4] libbpf: allow to opt-out from creating BPF maps
https://git.kernel.org/bpf/bpf-next/c/ec41817b4af5
- [bpf-next,4/4] selftests/bpf: test bpf_map__set_autocreate() and related log fixup logic
https://git.kernel.org/bpf/bpf-next/c/68964e155677
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-04-29 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 4:15 [PATCH bpf-next 0/4] libbpf: allow to opt-out from BPF map creation Andrii Nakryiko
2022-04-28 4:15 ` [PATCH bpf-next 1/4] libbpf: append "..." in fixed up log if CO-RE spec is truncated Andrii Nakryiko
2022-04-28 4:15 ` [PATCH bpf-next 2/4] libbpf: use libbpf_mem_ensure() when allocating new map Andrii Nakryiko
2022-04-28 4:15 ` [PATCH bpf-next 3/4] libbpf: allow to opt-out from creating BPF maps Andrii Nakryiko
2022-04-28 4:15 ` [PATCH bpf-next 4/4] selftests/bpf: test bpf_map__set_autocreate() and related log fixup logic Andrii Nakryiko
2022-04-29 3: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=165120241196.28026.9393761391052858735.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=kernel-team@fb.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;
as well as URLs for NNTP newsgroup(s).