From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: linux-next: Tree for Sep 28 (kernel/bpf/verifier.c)
Date: Mon, 28 Sep 2020 10:35:21 -0700 [thread overview]
Message-ID: <1762ab05-e8ba-8380-5c68-31642bb96ab4@infradead.org> (raw)
In-Reply-To: <20200928215551.2b882630@canb.auug.org.au>
On 9/28/20 4:55 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200925:
>
when CONFIG_NET is not set/enabled:
../kernel/bpf/verifier.c:3990: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],
^~~~~~~~~~~~
bpf_sock_ops
CC kernel/time/tick-oneshot.o
../kernel/bpf/verifier.c:3990: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],
^~~~~~~~~~~~~~~~~~~~~~~~~
PTR_TO_SOCK_COMMON
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2020-09-28 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 11:55 linux-next: Tree for Sep 28 Stephen Rothwell
2020-09-28 17:12 ` linux-next: Tree for Sep 28 (drivers/misc/hisi_hikey_usb.c ) Randy Dunlap
2020-09-28 17:35 ` Randy Dunlap [this message]
2020-09-28 18:35 ` linux-next: Tree for Sep 28 (drivers/media/platform/mtk-vcodec/) Randy Dunlap
2020-09-28 19:14 ` linux-next: Tree for Sep 28 (drivers/usb/dwc2/drd.o) Randy Dunlap
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=1762ab05-e8ba-8380-5c68-31642bb96ab4@infradead.org \
--to=rdunlap@infradead.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).