[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167752081731.14731.11660038530878470104.git-patchwork-notify@kernel.org>
Date: Mon, 27 Feb 2023 18:00:17 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Tiezhu Yang <yangtiezhu@...ngson.cn>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next v2 0/3] Fix some build errors for bpf selftest on
LoongArch
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.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!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists