Re: [PATCH bpf-next 0/4] selftests/bpf: Fix compilation with RELEASE=1

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Wed, 15 Jul 2026 13:21:59 +0200 you wrote:
> When compiling BPF selftests with RELEASE=1 (which most notably adds
> -O2), GCC reports several warnings. These are by default treated as
> errors and abort the compilation.
> 
> This series fixes all of the issues such that selftests can be compiled
> with RELEASE=1.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/4] selftests/bpf: Check malloc result with ASSERT_NEQ in test_loader
    https://git.kernel.org/bpf/bpf-next/c/40f986aed81f
  - [bpf-next,2/4] selftests/bpf: Check malloc result with ASSERT_NEQ in test_sha256
    https://git.kernel.org/bpf/bpf-next/c/eb5cd154f174
  - [bpf-next,3/4] selftests/bpf: Silence array bounds warning in global_map_resize
    https://git.kernel.org/bpf/bpf-next/c/dcd164ec67f8
  - [bpf-next,4/4] selftests/bpf: Silence maybe-uninitialized compiler warning in libarena
    https://git.kernel.org/bpf/bpf-next/c/5763790965eb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html