From: patchwork-bot+netdevbpf@kernel.org
To: Richard Palethorpe <rpalethorpe@suse.com>
Cc: arnd@arndb.de, kuba@kernel.org, davem@davemloft.net,
sgarzare@redhat.com, andraprs@amazon.com, edumazet@google.com,
arseny.krasnov@kaspersky.com, willemb@google.com,
deepa.kernel@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, rpalethorpe@richiejp.com
Subject: Re: [PATCH v3 1/2] vsock: Refactor vsock_*_getsockopt to resemble sock_getsockopt
Date: Fri, 08 Oct 2021 15:40:08 +0000 [thread overview]
Message-ID: <163370760863.7751.9806482518021821229.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211008100053.29806-1-rpalethorpe@suse.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 8 Oct 2021 11:00:52 +0100 you wrote:
> In preparation for sharing the implementation of sock_get_timeout.
>
> Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
> Cc: Richard Palethorpe <rpalethorpe@richiejp.com>
> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> ---
> net/vmw_vsock/af_vsock.c | 65 +++++++++++++++++-----------------------
> 1 file changed, 28 insertions(+), 37 deletions(-)
Here is the summary with links:
- [v3,1/2] vsock: Refactor vsock_*_getsockopt to resemble sock_getsockopt
https://git.kernel.org/netdev/net-next/c/685c3f2fba29
- [v3,2/2] vsock: Enable y2038 safe timeval for timeout
https://git.kernel.org/netdev/net-next/c/4c1e34c0dbff
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:[~2021-10-08 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 10:00 [PATCH v3 1/2] vsock: Refactor vsock_*_getsockopt to resemble sock_getsockopt Richard Palethorpe
2021-10-08 10:00 ` [PATCH v3 2/2] vsock: Enable y2038 safe timeval for timeout Richard Palethorpe
2021-10-08 15: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=163370760863.7751.9806482518021821229.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andraprs@amazon.com \
--cc=arnd@arndb.de \
--cc=arseny.krasnov@kaspersky.com \
--cc=davem@davemloft.net \
--cc=deepa.kernel@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rpalethorpe@richiejp.com \
--cc=rpalethorpe@suse.com \
--cc=sgarzare@redhat.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).