Hello: This series was applied to bpf/bpf-next.git (refs/heads/master): On Tue, 20 Jul 2021 09:49:50 +0100 you wrote: > This series aims to resolve further issues with the BTF typed data > dumping interfaces in libbpf. > > Compilation failures with use of __int128 on 32-bit platforms were > reported [1]. As a result, the use of __int128 in libbpf typed data > dumping is replaced with __u64 usage for bitfield manipulations. > In the case of 128-bit integer values, they are simply split into > two 64-bit hex values for display (patch 1). > > [...] Here is the summary with links: - [v2,bpf-next,1/3] libbpf: avoid use of __int128 in typed dump display https://git.kernel.org/bpf/bpf-next/c/a1d3cc3c5eca - [v2,bpf-next,2/3] selftests/bpf: add __int128-specific tests for typed data dump https://git.kernel.org/bpf/bpf-next/c/a17553dde294 - [v2,bpf-next,3/3] libbpf: propagate errors when retrieving enum value for typed data display https://git.kernel.org/bpf/bpf-next/c/720c29fca9fb You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html