mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, jhansen@vmware.com, davem@davemloft.net,
	decui@microsoft.com, aliguori@amazon.com, davdunc@amazon.com,
	andraprs@amazon.com, vkuznets@redhat.com, kuba@kernel.org,
	stefanha@redhat.com, linux-kernel@vger.kernel.org,
	graf@amazon.de
Subject: Re: [PATCH net] vsock: forward all packets to the host when no H2G is registered
Date: Sat, 14 Nov 2020 19:50:05 +0000	[thread overview]
Message-ID: <160538340528.29327.2961179379966892214.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201112133837.34183-1-sgarzare@redhat.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Thu, 12 Nov 2020 14:38:37 +0100 you wrote:
> Before commit c0cfa2d8a788 ("vsock: add multi-transports support"),
> if a G2H transport was loaded (e.g. virtio transport), every packets
> was forwarded to the host, regardless of the destination CID.
> The H2G transports implemented until then (vhost-vsock, VMCI) always
> responded with an error, if the destination CID was not
> VMADDR_CID_HOST.
> 
> [...]

Here is the summary with links:
  - [net] vsock: forward all packets to the host when no H2G is registered
    https://git.kernel.org/netdev/net/c/65b422d9b61b

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



  reply	other threads:[~2020-11-14 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 13:38 Stefano Garzarella
2020-11-14 19:50 ` patchwork-bot+netdevbpf [this message]
2020-11-19 14:03 ` Stefan Hajnoczi
2020-11-19 14:25   ` Alexander Graf
2020-11-19 14:41     ` Stefano Garzarella

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=160538340528.29327.2961179379966892214.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aliguori@amazon.com \
    --cc=andraprs@amazon.com \
    --cc=davdunc@amazon.com \
    --cc=davem@davemloft.net \
    --cc=decui@microsoft.com \
    --cc=graf@amazon.de \
    --cc=jhansen@vmware.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=vkuznets@redhat.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
all inboxes | Powered by JetHome®