From: patchwork-bot+netdevbpf@kernel.org
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, netdev@vger.kernel.org,
bpf@vger.kernel.org, kafai@fb.com, linux-next@vger.kernel.org
Subject: Re: [PATCH bpf-next] kernel/bpf/verifier: fix build when NET is not enabled
Date: Wed, 07 Oct 2020 18:00:03 +0000 [thread overview]
Message-ID: <160209360332.7046.6469450811216137483.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201007021613.13646-1-rdunlap@infradead.org>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Tue, 6 Oct 2020 19:16:13 -0700 you wrote:
> Fix build errors in kernel/bpf/verifier.c when CONFIG_NET is
> not enabled.
>
> ../kernel/bpf/verifier.c:3995:13: error: ‘btf_sock_ids’ undeclared here (not in a function); did you mean ‘bpf_sock_ops’?
> .btf_id = &btf_sock_ids[BTF_SOCK_TYPE_SOCK_COMMON],
>
> ../kernel/bpf/verifier.c:3995:26: error: ‘BTF_SOCK_TYPE_SOCK_COMMON’ undeclared here (not in a function); did you mean ‘PTR_TO_SOCK_COMMON’?
> .btf_id = &btf_sock_ids[BTF_SOCK_TYPE_SOCK_COMMON],
>
> [...]
Here is the summary with links:
- [bpf-next] kernel/bpf/verifier: fix build when NET is not enabled
https://git.kernel.org/bpf/bpf-next/c/49a2a4d4163f
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:[~2020-10-07 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 2:16 [PATCH bpf-next] kernel/bpf/verifier: fix build when NET is not enabled Randy Dunlap
2020-10-07 6:12 ` Yonghong Song
2020-10-07 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=160209360332.7046.6469450811216137483.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.