From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/3] block: Always compile virtio-blk dataplane
Date: Fri, 19 Sep 2014 11:04:42 +0200 [thread overview]
Message-ID: <541BF1AA.2080403@redhat.com> (raw)
In-Reply-To: <1410329871-28885-1-git-send-email-famz@redhat.com>
Il 10/09/2014 08:17, Fam Zheng ha scritto:
> v3: Fix -ENOBUFS.
> v2: Import virtio_vring.h.
>
> Fam Zheng (3):
> virtio: Import virtio_vring.h
> vring: Better error handling if num is too large
> block: Always compile virtio-blk dataplane
>
> configure | 21 +----
> hw/block/Makefile.objs | 2 +-
> hw/block/virtio-blk.c | 20 +----
> hw/net/vhost_net.c | 2 +-
> hw/virtio/Makefile.objs | 2 +-
> hw/virtio/dataplane/vring.c | 3 +-
> include/hw/virtio/dataplane/vring.h | 2 +-
> include/hw/virtio/virtio-blk.h | 2 -
> include/hw/virtio/virtio_ring.h | 167 ++++++++++++++++++++++++++++++++++++
> linux-headers/linux/vhost.h | 2 +-
> 10 files changed, 178 insertions(+), 45 deletions(-)
> create mode 100644 include/hw/virtio/virtio_ring.h
>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
next prev parent reply other threads:[~2014-09-19 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 6:17 [Qemu-devel] [PATCH v3 0/3] block: Always compile virtio-blk dataplane Fam Zheng
2014-09-10 6:17 ` [Qemu-devel] [PATCH v3 1/3] virtio: Import virtio_vring.h Fam Zheng
2014-09-10 6:17 ` [Qemu-devel] [PATCH v3 2/3] vring: Better error handling if num is too large Fam Zheng
2014-09-10 6:17 ` [Qemu-devel] [PATCH v3 3/3] block: Always compile virtio-blk dataplane Fam Zheng
2014-09-19 9:04 ` Paolo Bonzini [this message]
2014-09-19 12:37 ` [Qemu-devel] [PATCH v3 0/3] " Stefan Hajnoczi
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=541BF1AA.2080403@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.