MIME-Version: 1.0
References: <1677235015-21717-1-git-send-email-yangtiezhu@loongson.cn>
In-Reply-To: <1677235015-21717-1-git-send-email-yangtiezhu@loongson.cn>
From:   Andrii Nakryiko <andrii.nakryiko@gmail.com>
Date:   Mon, 27 Feb 2023 09:52:33 -0800
Message-ID: <CAEf4Bza9_LPMJnAGsPxDPEkY7JWL7PSwwZ7e_mHZGg32qaPvGQ@mail.gmail.com>
Subject: Re: [PATCH bpf-next v2 0/3] Fix some build errors for bpf selftest on LoongArch
To:     Tiezhu Yang <yangtiezhu@loongson.cn>
Cc:     Alexei Starovoitov <ast@kernel.org>,
        Daniel Borkmann <daniel@iogearbox.net>,
        Andrii Nakryiko <andrii@kernel.org>, bpf@vger.kernel.org,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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
>