From: patchwork-bot+netdevbpf@kernel.org
To: Florent Revest <revest@chromium.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kpsingh@chromium.org, rdunlap@infradead.org,
kafai@fb.com, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, lkp@intel.com
Subject: Re: [PATCH bpf-next v3] bpf: Only provide bpf_sock_from_file with CONFIG_NET
Date: Wed, 09 Dec 2020 02:30:06 +0000 [thread overview]
Message-ID: <160748100661.25606.9093135909734120756.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201208173623.1136863-1-revest@chromium.org>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Tue, 8 Dec 2020 18:36:23 +0100 you wrote:
> This moves the bpf_sock_from_file definition into net/core/filter.c
> which only gets compiled with CONFIG_NET and also moves the helper proto
> usage next to other tracing helpers that are conditional on CONFIG_NET.
>
> This avoids
> ld: kernel/trace/bpf_trace.o: in function `bpf_sock_from_file':
> bpf_trace.c:(.text+0xe23): undefined reference to `sock_from_file'
> When compiling a kernel with BPF and without NET.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] bpf: Only provide bpf_sock_from_file with CONFIG_NET
https://git.kernel.org/bpf/bpf-next/c/b60da4955f53
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-12-09 2:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 17:36 Florent Revest
2020-12-08 20:06 ` Randy Dunlap
2020-12-08 20:19 ` Florent Revest
2020-12-08 20:54 ` Martin KaFai Lau
2020-12-08 21:58 ` KP Singh
2020-12-09 2:30 ` 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=160748100661.25606.9093135909734120756.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=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rdunlap@infradead.org \
--cc=revest@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome