Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Mon, 24 May 2021 20:59:30 -0700 you wrote:
> Implement error reporting changes discussed in "Libbpf: the road to v1.0"
> ([0]) document.
>
> Libbpf gets a new API, libbpf_set_strict_mode() which accepts a set of flags
> that turn on a set of libbpf 1.0 changes, that might be potentially breaking.
> It's possible to opt-in into all current and future 1.0 features by specifying
> LIBBPF_STRICT_ALL flag.
>
> [...]
Here is the summary with links:
- [v2,bpf-next,1/5] libbpf: add libbpf_set_strict_mode() API to turn on libbpf 1.0 behaviors
https://git.kernel.org/bpf/bpf-next/c/5981881d21df
- [v2,bpf-next,2/5] selftests/bpf: turn on libbpf 1.0 mode and fix all IS_ERR checks
https://git.kernel.org/bpf/bpf-next/c/bad2e478af3b
- [v2,bpf-next,3/5] libbpf: streamline error reporting for low-level APIs
https://git.kernel.org/bpf/bpf-next/c/f12b65432728
- [v2,bpf-next,4/5] libbpf: streamline error reporting for high-level APIs
https://git.kernel.org/bpf/bpf-next/c/e9fc3ce99b34
- [v2,bpf-next,5/5] bpftool: set errno on skeleton failures and propagate errors
https://git.kernel.org/bpf/bpf-next/c/9c6c0449deb4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
