From: patchwork-bot+netdevbpf@kernel.org
To: Krasnov Arseniy Vladimirovich <AVKrasnov@sberdevices.ru>
Cc: sgarzare@redhat.com, oxffffaa@gmail.com,
DDRokosov@sberdevices.ru, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/2] af_vsock: add two new tests for SOCK_SEQPACKET
Date: Fri, 18 Mar 2022 15:30:14 +0000 [thread overview]
Message-ID: <164761741491.31796.2986635907714259777.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <97d6d8c6-f7b2-1b03-a3d9-f312c33134ec@sberdevices.ru>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 17 Mar 2022 08:29:50 +0000 you wrote:
> This adds two tests: for receive timeout and reading to invalid
> buffer provided by user. I forgot to put both patches to main
> patchset.
>
> Arseniy Krasnov(2):
>
> af_vsock: SOCK_SEQPACKET receive timeout test
> af_vsock: SOCK_SEQPACKET broken buffer test
>
> [...]
Here is the summary with links:
- [net-next,v4,1/2] af_vsock: SOCK_SEQPACKET receive timeout test
https://git.kernel.org/netdev/net-next/c/efb3719f4ab0
- [net-next,v4,2/2] af_vsock: SOCK_SEQPACKET broken buffer test
https://git.kernel.org/netdev/net-next/c/e89600ebeeb1
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:[~2022-03-18 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 8:29 [PATCH net-next v4 0/2] af_vsock: add two new tests for SOCK_SEQPACKET Krasnov Arseniy Vladimirovich
2022-03-17 8:31 ` [PATCH net-next v4 1/2] af_vsock: SOCK_SEQPACKET receive timeout test Krasnov Arseniy Vladimirovich
2022-03-17 8:49 ` Stefano Garzarella
2022-03-17 8:33 ` [PATCH net-next v4 2/2] af_vsock: SOCK_SEQPACKET broken buffer test Krasnov Arseniy Vladimirovich
2022-03-18 5:05 ` [PATCH net-next v4 0/2] af_vsock: add two new tests for SOCK_SEQPACKET Krasnov Arseniy Vladimirovich
2022-03-18 15:30 ` 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=164761741491.31796.2986635907714259777.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=AVKrasnov@sberdevices.ru \
--cc=DDRokosov@sberdevices.ru \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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