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/9] Misc libbpf fixes and small improvements
Date: Mon, 09 May 2022 15:20:12 +0000 [thread overview]
Message-ID: <165210961287.23832.9091333940199617708.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220509004148.1801791-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sun, 8 May 2022 17:41:39 -0700 you wrote:
> This patch set is a mix of mostly mutually unrelated libbpf and selftests
> fixes and improvements. Individual patches provide details on each one.
>
> Andrii Nakryiko (9):
> selftests/bpf: prevent skeleton generation race
> libbpf: make __kptr and __kptr_ref unconditionally use btf_type_tag()
> attr
> libbpf: improve usability of field-based CO-RE helpers
> selftests/bpf: use both syntaxes for field-based CO-RE helpers
> libbpf: complete field-based CO-RE helpers with field offset helper
> selftests/bpf: add bpf_core_field_offset() tests
> libbpf: provide barrier() and barrier_var() in bpf_helpers.h
> libbpf: automatically fix up BPF_MAP_TYPE_RINGBUF size, if necessary
> selftests/bpf: test libbpf's ringbuf size fix up logic
>
> [...]
Here is the summary with links:
- [bpf-next,1/9] selftests/bpf: prevent skeleton generation race
https://git.kernel.org/bpf/bpf-next/c/1e2666e029e5
- [bpf-next,2/9] libbpf: make __kptr and __kptr_ref unconditionally use btf_type_tag() attr
https://git.kernel.org/bpf/bpf-next/c/8e2f618e8be6
- [bpf-next,3/9] libbpf: improve usability of field-based CO-RE helpers
https://git.kernel.org/bpf/bpf-next/c/73d0280f6b79
- [bpf-next,4/9] selftests/bpf: use both syntaxes for field-based CO-RE helpers
https://git.kernel.org/bpf/bpf-next/c/2a4ca46b7d2a
- [bpf-next,5/9] libbpf: complete field-based CO-RE helpers with field offset helper
https://git.kernel.org/bpf/bpf-next/c/7715f549a9d8
- [bpf-next,6/9] selftests/bpf: add bpf_core_field_offset() tests
https://git.kernel.org/bpf/bpf-next/c/785c3342cf6c
- [bpf-next,7/9] libbpf: provide barrier() and barrier_var() in bpf_helpers.h
https://git.kernel.org/bpf/bpf-next/c/f760d0537925
- [bpf-next,8/9] libbpf: automatically fix up BPF_MAP_TYPE_RINGBUF size, if necessary
https://git.kernel.org/bpf/bpf-next/c/0087a681fa8c
- [bpf-next,9/9] selftests/bpf: test libbpf's ringbuf size fix up logic
https://git.kernel.org/bpf/bpf-next/c/7b3a06382442
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-05-09 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 0:41 [PATCH bpf-next 0/9] Misc libbpf fixes and small improvements Andrii Nakryiko
2022-05-09 0:41 ` [PATCH bpf-next 1/9] selftests/bpf: prevent skeleton generation race Andrii Nakryiko
2022-05-09 0:41 ` [PATCH bpf-next 2/9] libbpf: make __kptr and __kptr_ref unconditionally use btf_type_tag() attr Andrii Nakryiko
2022-12-26 11:34 ` [PATCH bpf-next 2/9] libbpf: make __kptr and __kptr_ref Rong Tao
2022-12-28 19:03 ` Yonghong Song
2022-05-09 0:41 ` [PATCH bpf-next 3/9] libbpf: improve usability of field-based CO-RE helpers Andrii Nakryiko
2022-05-09 0:41 ` [PATCH bpf-next 4/9] selftests/bpf: use both syntaxes for " Andrii Nakryiko
2022-05-09 0:41 ` [PATCH bpf-next 5/9] libbpf: complete field-based CO-RE helpers with field offset helper Andrii Nakryiko
2022-05-09 0:41 ` [PATCH bpf-next 6/9] selftests/bpf: add bpf_core_field_offset() tests Andrii Nakryiko
2022-05-09 0:41 ` [PATCH bpf-next 7/9] libbpf: provide barrier() and barrier_var() in bpf_helpers.h Andrii Nakryiko
2022-05-09 0:41 ` [PATCH bpf-next 8/9] libbpf: automatically fix up BPF_MAP_TYPE_RINGBUF size, if necessary Andrii Nakryiko
2022-05-10 15:34 ` Nathan Chancellor
2022-05-10 18:47 ` Andrii Nakryiko
2022-05-09 0:41 ` [PATCH bpf-next 9/9] selftests/bpf: test libbpf's ringbuf size fix up logic Andrii Nakryiko
2022-05-09 15: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=165210961287.23832.9091333940199617708.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