Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Mon, 14 Dec 2020 18:11:17 +0200 you wrote:

vsock enables communication between virtual machines and the host they are
running on. Nested VMs can be setup to use vsock channels, as the multi
transport support has been available in the mainline since the v5.5 Linux kernel
has been released.

Implicitly, if no host->guest vsock transport is loaded, all the vsock packets
are forwarded to the host. This behavior can be used to setup communication
channels between sibling VMs that are running on the same host. One example can
be the vsock channels that can be established within AWS Nitro Enclaves
(see Documentation/virt/ne_overview.rst).

[...]

Here is the summary with links:
  - [net-next,v4,1/5] vm_sockets: Add flags field in the vsock address data structure
    https://git.kernel.org/netdev/net-next/c/dc8eeef73b63
  - [net-next,v4,2/5] vm_sockets: Add VMADDR_FLAG_TO_HOST vsock flag
    https://git.kernel.org/netdev/net-next/c/caaf95e0f23f
  - [net-next,v4,3/5] vsock_addr: Check for supported flag values
    https://git.kernel.org/netdev/net-next/c/cada7ccd9dc7
  - [net-next,v4,4/5] af_vsock: Set VMADDR_FLAG_TO_HOST flag on the receive path
    https://git.kernel.org/netdev/net-next/c/1b5f2ab98e7f
  - [net-next,v4,5/5] af_vsock: Assign the vsock transport considering the vsock address flags
    https://git.kernel.org/netdev/net-next/c/7f816984f439

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html