From: Stefano Garzarella <sgarzare@redhat.com>
To: Simon Horman <horms@kernel.org>
Cc: Yue Haibing <yuehaibing@huawei.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, 4 Aug 2023 09:50:06 +0200 [thread overview]
Message-ID: <xjs5cdmrcnsnzvbezd24lzvb4fgoofkyamvbxzbcwpetslhizc@seph4jwbpziv> (raw)
In-Reply-To: <ZMwBFdw8BTno3dn2@kernel.org>
On Thu, Aug 03, 2023 at 09:33:41PM +0200, Simon Horman wrote:
>On Thu, Aug 03, 2023 at 09:45:07PM +0800, Yue Haibing 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>
>
>Hi Yue Haibing,
>
>FWIIW, I think this should be targeted at net-next.
Yep, please send to net-next.
Looks good also to me:
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
WARNING: multiple messages have this Message-ID (diff)
From: Stefano Garzarella <sgarzare@redhat.com>
To: Simon Horman <horms@kernel.org>
Cc: bobby.eshleman@bytedance.com, netdev@vger.kernel.org,
Yue Haibing <yuehaibing@huawei.com>,
virtualization@lists.linux-foundation.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net
Subject: Re: [PATCH -next] af_vsock: Remove unused declaration vsock_release_pending()/vsock_init_tap()
Date: Fri, 4 Aug 2023 09:50:06 +0200 [thread overview]
Message-ID: <xjs5cdmrcnsnzvbezd24lzvb4fgoofkyamvbxzbcwpetslhizc@seph4jwbpziv> (raw)
In-Reply-To: <ZMwBFdw8BTno3dn2@kernel.org>
On Thu, Aug 03, 2023 at 09:33:41PM +0200, Simon Horman wrote:
>On Thu, Aug 03, 2023 at 09:45:07PM +0800, Yue Haibing 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>
>
>Hi Yue Haibing,
>
>FWIIW, I think this should be targeted at net-next.
Yep, please send to net-next.
Looks good also to me:
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-08-04 7:50 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 [this message]
2023-08-04 7:50 ` Stefano Garzarella
2023-08-04 22:40 ` patchwork-bot+netdevbpf
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=xjs5cdmrcnsnzvbezd24lzvb4fgoofkyamvbxzbcwpetslhizc@seph4jwbpziv \
--to=sgarzare@redhat.com \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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.