public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix•com>
To: Paul Durrant <paul.durrant@citrix•com>
Cc: <xen-devel@lists•xenproject.org>, <netdev@vger•kernel.org>,
	Wei Liu <wei.liu2@citrix•com>
Subject: Re: [PATCH net-next v4 2/4] xen-netback: add control protocol implementation
Date: Fri, 13 May 2016 12:20:11 +0100	[thread overview]
Message-ID: <20160513112011.GB5442@citrix.com> (raw)
In-Reply-To: <1463128649-20832-3-git-send-email-paul.durrant@citrix.com>

On Fri, May 13, 2016 at 09:37:27AM +0100, Paul Durrant wrote:
> My recent patch to include/xen/interface/io/netif.h defines a new shared
> ring (in addition to the rx and tx rings) for passing control messages
> from a VM frontend driver to a backend driver.
> 
> A previous patch added the necessary boilerplate for mapping the control
> ring from the frontend, should it be created. This patch adds
> implementations for each of the defined protocol messages.
> 
> Signed-off-by: Paul Durrant <paul.durrant@citrix•com>
> Cc: Wei Liu <wei.liu2@citrix•com>

Acked-by: Wei Liu <wei.liu2@citrix•com>

  reply	other threads:[~2016-05-13 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13  8:37 [PATCH net-next v4 0/4] xen-netback: support for control ring Paul Durrant
2016-05-13  8:37 ` [PATCH net-next v4 1/4] xen-netback: add control ring boilerplate Paul Durrant
2016-05-13  8:37 ` [PATCH net-next v4 2/4] xen-netback: add control protocol implementation Paul Durrant
2016-05-13 11:20   ` Wei Liu [this message]
2016-05-13  8:37 ` [PATCH net-next v4 3/4] xen-netback: pass hash value to the frontend Paul Durrant
2016-05-13  8:37 ` [PATCH net-next v4 4/4] xen-netback: use hash value from " Paul Durrant
2016-05-16 17:36 ` [PATCH net-next v4 0/4] xen-netback: support for control ring David Miller

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=20160513112011.GB5442@citrix.com \
    --to=wei.liu2@citrix$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=paul.durrant@citrix$(echo .)com \
    --cc=xen-devel@lists$(echo .)xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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