Linux virtualization list
 help / color / mirror / Atom feed
From: Asias He <asias@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: virtualization@lists.linux-foundation.org,
	target-devel@vger.kernel.org, kvm@vger.kernel.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 0/3] vhost cleanups and separate module
Date: Mon, 6 May 2013 16:15:39 +0800	[thread overview]
Message-ID: <20130506081538.GA3389@hj.localdomain> (raw)
In-Reply-To: <87sj20prhj.fsf@rustcorp.com.au>

Hello Rusty, 

On Mon, May 06, 2013 at 03:41:36PM +0930, Rusty Russell wrote:
> Asias He <asias@redhat.com> writes:
> > Asias He (3):
> >   vhost: Remove vhost_enable_zcopy in vhost.h
> >   vhost: Move VHOST_NET_FEATURES to net.c
> >   vhost: Make vhost a separate module
> 
> I like these cleanups, MST pleasee apply.
> 
> I have some other cleanups which are on hold for the moment pending
> MST's vhost_net simplification.  MST, how's that going?

Do you mean patches in your rusty/vringh branch? I want to do the frame
assumption conversion for vhost-scsi on top of the vringh series.

> Thanks,
> Rusty.

-- 
Asias

  reply	other threads:[~2013-05-06  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03  5:34 [PATCH 0/3] vhost cleanups and separate module Asias He
2013-05-03  5:34 ` [PATCH 1/3] vhost: Remove vhost_enable_zcopy in vhost.h Asias He
2013-05-03  5:34 ` [PATCH 2/3] vhost: Move VHOST_NET_FEATURES to net.c Asias He
2013-05-03  5:34 ` [PATCH 3/3] vhost: Make vhost a separate module Asias He
2013-05-06  6:11 ` [PATCH 0/3] vhost cleanups and " Rusty Russell
2013-05-06  8:15   ` Asias He [this message]
2013-05-06  9:19   ` Michael S. Tsirkin
2013-05-07  4:43     ` Rusty Russell
2013-05-07 12:44       ` Michael S. Tsirkin
2013-05-13  1:05         ` Rusty Russell
2013-05-13  3:39         ` Jason Wang

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=20130506081538.GA3389@hj.localdomain \
    --to=asias@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=target-devel@vger.kernel.org \
    --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