Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH bpf-next v3] bpf: Only provide bpf_sock_from_file with
 CONFIG_NET
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <160748100661.25606.9093135909734120756.git-patchwork-notify@kernel.org>
Date:   Wed, 09 Dec 2020 02:30:06 +0000
References: <20201208173623.1136863-1-revest@chromium.org>
In-Reply-To: <20201208173623.1136863-1-revest@chromium.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
Precedence: bulk

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