From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bobby.eshleman@bytedance.com, kuba@kernel.org, horms@kernel.org,
pabeni@redhat.com, mst@redhat.com,
virtualization@lists.linux.dev, bpf@vger.kernel.org,
davem@davemloft.net, edumazet@google.com
Subject: Re: [PATCH net] vsock: fix `vsock_proto` declaration
Date: Tue, 08 Jul 2025 00:43:27 +0000 [thread overview]
Message-ID: <175193540775.3455828.16493006355772974081.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250703112329.28365-1-sgarzare@redhat.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 3 Jul 2025 13:23:29 +0200 you wrote:
> From: Stefano Garzarella <sgarzare@redhat.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
prev parent reply other threads:[~2025-07-08 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 11:23 [PATCH net] vsock: fix `vsock_proto` declaration Stefano Garzarella
2025-07-03 11:24 ` Michael S. Tsirkin
2025-07-08 0:43 ` 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=175193540775.3455828.16493006355772974081.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bobby.eshleman@bytedance.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux.dev \
/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