Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH bpf-next v2 0/3] Fix some build errors for bpf selftest on
 LoongArch
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <167752081731.14731.11660038530878470104.git-patchwork-notify@kernel.org>
Date:   Mon, 27 Feb 2023 18:00:17 +0000
References: <1677235015-21717-1-git-send-email-yangtiezhu@loongson.cn>
In-Reply-To: <1677235015-21717-1-git-send-email-yangtiezhu@loongson.cn>
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
Precedence: bulk

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