Message ID | 1677235015-21717-1-git-send-email-yangtiezhu@loongson.cn (mailing list archive) |
---|---|
Headers | show |
Series | Fix some build errors for bpf selftest on LoongArch | expand |
On Fri, Feb 24, 2023 at 2:37 AM Tiezhu Yang <yangtiezhu@loongson.cn> wrote: > > v2: Modify patch #3 to avoid breaking user_ringbuf test on x86 > > Tiezhu Yang (3): > libbpf: Use struct user_pt_regs to define __PT_REGS_CAST() for > LoongArch > selftests/bpf: Check __TARGET_ARCH_loongarch if target is bpf for > LoongArch > selftests/bpf: Use __NR_prlimit64 instead of __NR_getrlimit in > user_ringbuf test I've applied patches 1 and 3 to bpf-next, but we can't do what patch 2 does. Also, please provide a proper cover letter message next time, just version log isn't enough. > > tools/include/uapi/asm/bitsperlong.h | 2 +- > tools/lib/bpf/bpf_tracing.h | 2 ++ > tools/testing/selftests/bpf/prog_tests/user_ringbuf.c | 2 +- > tools/testing/selftests/bpf/progs/user_ringbuf_success.c | 2 +- > 4 files changed, 5 insertions(+), 3 deletions(-) > > -- > 2.1.0 >
Hello: This series was applied to bpf/bpf-next.git (master) by Andrii Nakryiko <andrii@kernel.org>: On Fri, 24 Feb 2023 18:36:52 +0800 you wrote: > v2: Modify patch #3 to avoid breaking user_ringbuf test on x86 > > Tiezhu Yang (3): > libbpf: Use struct user_pt_regs to define __PT_REGS_CAST() for > LoongArch > selftests/bpf: Check __TARGET_ARCH_loongarch if target is bpf for > LoongArch > selftests/bpf: Use __NR_prlimit64 instead of __NR_getrlimit in > user_ringbuf test > > [...] Here is the summary with links: - [bpf-next,v2,1/3] libbpf: Use struct user_pt_regs to define __PT_REGS_CAST() for LoongArch https://git.kernel.org/bpf/bpf-next/c/29c66ad1c3ad - [bpf-next,v2,2/3] selftests/bpf: Check __TARGET_ARCH_loongarch if target is bpf for LoongArch (no matching commit) - [bpf-next,v2,3/3] selftests/bpf: Use __NR_prlimit64 instead of __NR_getrlimit in user_ringbuf test https://git.kernel.org/bpf/bpf-next/c/84c22fa83f9c You are awesome, thank you!