From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, songliubraving@fb.com
Subject: Re: [PATCH bpf-next] bpf: fix build failure for kernel/trace/bpf_trace.c with CONFIG_NET=n
Date: Wed, 07 Oct 2020 18:00:03 +0000 [thread overview]
Message-ID: <160209360336.7046.15696471491976584744.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201007062933.3425899-1-yhs@fb.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Tue, 6 Oct 2020 23:29:33 -0700 you wrote:
> When CONFIG_NET is not defined, I hit the following build error:
> kernel/trace/bpf_trace.o:(.rodata+0x110): undefined reference to `bpf_prog_test_run_raw_tp'
>
> Commit 1b4d60ec162f ("bpf: Enable BPF_PROG_TEST_RUN for raw_tracepoint")
> added test_run support for raw_tracepoint in /kernel/trace/bpf_trace.c.
> But the test_run function bpf_prog_test_run_raw_tp is defined in
> net/bpf/test_run.c, only available with CONFIG_NET=y.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: fix build failure for kernel/trace/bpf_trace.c with CONFIG_NET=n
https://git.kernel.org/bpf/bpf-next/c/ebfb4d40ed9d
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: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 6:29 [PATCH bpf-next] bpf: fix build failure for kernel/trace/bpf_trace.c with CONFIG_NET=n 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=160209360336.7046.15696471491976584744.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=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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).