From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next 0/6] Provide bpf_for() and bpf_for_each() by libbpf
Date: Tue, 18 Apr 2023 20:00:20 +0000 [thread overview]
Message-ID: <168184802046.10886.237770748508440656.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230418002148.3255690-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 17 Apr 2023 17:21:42 -0700 you wrote:
> This patch set moves bpf_for(), bpf_for_each(), and bpf_repeat() macros from
> selftests-internal bpf_misc.h header to libbpf-provided bpf_helpers.h header.
> To do this in a way to allow users to feature-detect and guard such
> bpf_for()/bpf_for_each() uses on old kernels we also extend libbpf to improve
> unresolved kfunc calls handling and reporting. This lets us mark
> bpf_iter_num_{new,next,destroy}() declarations as __weak, and thus not fail
> program loading outright if such kfuncs are missing on the host kernel.
>
> [...]
Here is the summary with links:
- [bpf-next,1/6] libbpf: misc internal libbpf clean ups around log fixup
https://git.kernel.org/bpf/bpf-next/c/3055ddd654f6
- [bpf-next,2/6] libbpf: report vmlinux vs module name when dealing with ksyms
https://git.kernel.org/bpf/bpf-next/c/f709160d1724
- [bpf-next,3/6] libbpf: improve handling of unresolved kfuncs
https://git.kernel.org/bpf/bpf-next/c/05b6f766b25c
- [bpf-next,4/6] selftests/bpf: add missing __weak kfunc log fixup test
https://git.kernel.org/bpf/bpf-next/c/30bbfe3236b0
- [bpf-next,5/6] libbpf: move bpf_for(), bpf_for_each(), and bpf_repeat() into bpf_helpers.h
https://git.kernel.org/bpf/bpf-next/c/c5e647416708
- [bpf-next,6/6] libbpf: mark bpf_iter_num_{new,next,destroy} as __weak
https://git.kernel.org/bpf/bpf-next/c/94dccba79520
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-18 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 0:21 [PATCH bpf-next 0/6] Provide bpf_for() and bpf_for_each() by libbpf Andrii Nakryiko
2023-04-18 0:21 ` [PATCH bpf-next 1/6] libbpf: misc internal libbpf clean ups around log fixup Andrii Nakryiko
2023-04-18 0:21 ` [PATCH bpf-next 2/6] libbpf: report vmlinux vs module name when dealing with ksyms Andrii Nakryiko
2023-04-18 0:21 ` [PATCH bpf-next 3/6] libbpf: improve handling of unresolved kfuncs Andrii Nakryiko
2023-04-18 1:10 ` Alexei Starovoitov
2023-04-18 18:10 ` Andrii Nakryiko
2023-04-18 18:14 ` Alexei Starovoitov
2023-04-18 18:45 ` Andrii Nakryiko
2023-04-18 0:21 ` [PATCH bpf-next 4/6] selftests/bpf: add missing __weak kfunc log fixup test Andrii Nakryiko
2023-04-18 0:21 ` [PATCH bpf-next 5/6] libbpf: move bpf_for(), bpf_for_each(), and bpf_repeat() into bpf_helpers.h Andrii Nakryiko
2023-04-18 0:21 ` [PATCH bpf-next 6/6] libbpf: mark bpf_iter_num_{new,next,destroy} as __weak Andrii Nakryiko
2023-04-18 20:00 ` 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=168184802046.10886.237770748508440656.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@meta.com \
--cc=martin.lau@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