Re: [PATCH bpf-next v4 0/2] tools/resolve_btfids: fix cross-compilation to non-host endianness

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@xxxxxxxxxx>:

On Tue,  6 Feb 2024 13:46:08 +0100 you wrote:
> The .BTF_ids section is pre-filled with zeroed BTF ID entries during the
> build and afterwards patched by resolve_btfids with correct values.
> Since resolve_btfids always writes in host-native endianness, it relies
> on libelf to do the translation when the target ELF is cross-compiled to
> a different endianness (this was introduced in commit 61e8aeda9398
> ("bpf: Fix libelf endian handling in resolv_btfids")).
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/2] tools/resolve_btfids: Refactor set sorting with types from btf_ids.h
    https://git.kernel.org/bpf/bpf-next/c/9707ac4fe2f5
  - [bpf-next,v4,2/2] tools/resolve_btfids: fix cross-compilation to non-host endianness
    https://git.kernel.org/bpf/bpf-next/c/903fad439466

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






[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux