From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
lixuefeng@loongson.cn, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] bpf, mips: Fix build errors about __NR_bpf undeclared
Date: Fri, 26 Nov 2021 21:20:08 +0000 [thread overview]
Message-ID: <163796160866.30899.10399099274793745280.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1637804167-8323-1-git-send-email-yangtiezhu@loongson.cn>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 25 Nov 2021 09:36:07 +0800 you wrote:
> Add the __NR_bpf definitions to fix the following build errors for mips.
>
> $ cd tools/bpf/bpftool
> $ make
> [...]
> bpf.c:54:4: error: #error __NR_bpf not defined. libbpf does not support your arch.
> # error __NR_bpf not defined. libbpf does not support your arch.
> ^~~~~
> bpf.c: In function ‘sys_bpf’:
> bpf.c:66:17: error: ‘__NR_bpf’ undeclared (first use in this function); did you mean ‘__NR_brk’?
> return syscall(__NR_bpf, cmd, attr, size);
> ^~~~~~~~
> __NR_brk
> [...]
> In file included from gen_loader.c:15:0:
> skel_internal.h: In function ‘skel_sys_bpf’:
> skel_internal.h:53:17: error: ‘__NR_bpf’ undeclared (first use in this function); did you mean ‘__NR_brk’?
> return syscall(__NR_bpf, cmd, attr, size);
> ^~~~~~~~
> __NR_brk
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf, mips: Fix build errors about __NR_bpf undeclared
https://git.kernel.org/bpf/bpf-next/c/e32cb12ff52a
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:[~2021-11-26 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 1:36 [PATCH bpf-next v2] bpf, mips: Fix build errors about __NR_bpf undeclared Tiezhu Yang
2021-11-25 23:05 ` Daniel Borkmann
2021-11-26 1:22 ` Andrii Nakryiko
2021-11-26 21:20 ` 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=163796160866.30899.10399099274793745280.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=lixuefeng@loongson.cn \
--cc=netdev@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