[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175193540775.3455828.16493006355772974081.git-patchwork-notify@kernel.org>
Date: Tue, 08 Jul 2025 00:43:27 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Stefano Garzarella <sgarzare@...hat.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
bobby.eshleman@...edance.com, kuba@...nel.org, horms@...nel.org,
pabeni@...hat.com, mst@...hat.com, virtualization@...ts.linux.dev,
bpf@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com
Subject: Re: [PATCH net] vsock: fix `vsock_proto` declaration
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Thu, 3 Jul 2025 13:23:29 +0200 you wrote:
> From: Stefano Garzarella <sgarzare@...hat.com>
>
> From commit 634f1a7110b4 ("vsock: support sockmap"), `struct proto
> vsock_proto`, defined in af_vsock.c, is not static anymore, since it's
> used by vsock_bpf.c.
>
> If CONFIG_BPF_SYSCALL is not defined, `make C=2` will print a warning:
> $ make O=build C=2 W=1 net/vmw_vsock/
> ...
> CC [M] net/vmw_vsock/af_vsock.o
> CHECK ../net/vmw_vsock/af_vsock.c
> ../net/vmw_vsock/af_vsock.c:123:14: warning: symbol 'vsock_proto' was not declared. Should it be static?
>
> [...]
Here is the summary with links:
- [net] vsock: fix `vsock_proto` declaration
https://git.kernel.org/netdev/net/c/1e3b66e32601
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists