From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/3] Fix some build errors for bpf selftest on LoongArch
Date: Mon, 27 Feb 2023 18:00:17 +0000 [thread overview]
Message-ID: <167752081731.14731.11660038530878470104.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1677235015-21717-1-git-send-email-yangtiezhu@loongson.cn>
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!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-27 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 10:36 [PATCH bpf-next v2 0/3] Fix some build errors for bpf selftest on LoongArch Tiezhu Yang
2023-02-24 10:36 ` [PATCH bpf-next v2 1/3] libbpf: Use struct user_pt_regs to define __PT_REGS_CAST() for LoongArch Tiezhu Yang
2023-02-24 10:36 ` [PATCH bpf-next v2 2/3] selftests/bpf: Check __TARGET_ARCH_loongarch if target is bpf " Tiezhu Yang
2023-02-27 17:40 ` Andrii Nakryiko
2023-02-24 10:36 ` [PATCH bpf-next v2 3/3] selftests/bpf: Use __NR_prlimit64 instead of __NR_getrlimit in user_ringbuf test Tiezhu Yang
2023-02-27 17:52 ` [PATCH bpf-next v2 0/3] Fix some build errors for bpf selftest on LoongArch Andrii Nakryiko
2023-02-27 18:00 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=167752081731.14731.11660038530878470104.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yangtiezhu@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox