From: patchwork-bot+netdevbpf@kernel.org
To: Yue Haibing <yuehaibing@huawei.com>
Cc: sgarzare@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, bobby.eshleman@bytedance.com,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [PATCH -next] af_vsock: Remove unused declaration vsock_release_pending()/vsock_init_tap()
Date: Fri, 04 Aug 2023 22:40:23 +0000 [thread overview]
Message-ID: <169118882376.4114.10938724911991254974.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230803134507.22660-1-yuehaibing@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 3 Aug 2023 21:45:07 +0800 you wrote:
> Commit d021c344051a ("VSOCK: Introduce VM Sockets") declared but never implemented
> vsock_release_pending(). Also vsock_init_tap() never implemented since introduction
> in commit 531b374834c8 ("VSOCK: Add vsockmon tap functions").
>
> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
> ---
> include/net/af_vsock.h | 2 --
> 1 file changed, 2 deletions(-)
Here is the summary with links:
- [-next] af_vsock: Remove unused declaration vsock_release_pending()/vsock_init_tap()
https://git.kernel.org/netdev/net-next/c/781486e415dc
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:[~2023-08-04 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 13:45 [PATCH -next] af_vsock: Remove unused declaration vsock_release_pending()/vsock_init_tap() Yue Haibing via Virtualization
2023-08-03 13:45 ` Yue Haibing
2023-08-03 19:33 ` Simon Horman
2023-08-04 7:50 ` Stefano Garzarella
2023-08-04 7:50 ` Stefano Garzarella
2023-08-04 22:40 ` 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=169118882376.4114.10938724911991254974.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=yuehaibing@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.