From: "Michael S. Tsirkin" <mst@redhat.com>
To: Shannon Zhao <shannon.zhao@linaro.org>
Cc: peter.maydell@linaro.org, hangaohuai@huawei.com,
peter.huangpeng@huawei.com, qemu-devel@nongnu.org,
zhaoshenglong@huawei.com, cornelia.huck@de.ibm.com,
pbonzini@redhat.com, christoffer.dall@linaro.org
Subject: Re: [Qemu-devel] [PATCH v3 2/2] virtio-scsi: Move DEFINE_VIRTIO_SCSI_FEATURES to virtio-scsi
Date: Tue, 28 Apr 2015 07:55:18 +0200 [thread overview]
Message-ID: <20150428075441-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <553ED515.400@linaro.org>
Pong.
You responded to Cornelia's comments on patch 1/2
with "ok will add".
I expected v4.
On Tue, Apr 28, 2015 at 08:32:21AM +0800, Shannon Zhao wrote:
> Ping?
>
> On 2015/4/21 18:51, shannon.zhao@linaro.org wrote:
> > From: Shannon Zhao <shannon.zhao@linaro.org>
> >
> > Move DEFINE_VIRTIO_SCSI_FEATURES to the backend virtio-scsi.
> > The transports just sync the host features from backend.
> >
> > Signed-off-by: Shannon Zhao <zhaoshenglong@huawei.com>
> > Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
> > ---
> > hw/s390x/s390-virtio-bus.c | 1 -
> > hw/s390x/virtio-ccw.c | 1 -
> > hw/scsi/virtio-scsi.c | 5 +++++
> > hw/virtio/virtio-pci.c | 1 -
> > include/hw/virtio/virtio-scsi.h | 1 +
> > 5 files changed, 6 insertions(+), 3 deletions(-)
>
> --
> Shannon
next prev parent reply other threads:[~2015-04-28 5:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 10:51 [Qemu-devel] [PATCH v3 0/2] virtio: Move host features to backends shannon.zhao
2015-04-21 10:51 ` [Qemu-devel] [PATCH v3 1/2] hw/net/virtio-net: Move DEFINE_VIRTIO_NET_FEATURES to virtio-net shannon.zhao
2015-04-22 14:24 ` Cornelia Huck
2015-04-23 0:31 ` Shannon Zhao
2015-04-21 10:51 ` [Qemu-devel] [PATCH v3 2/2] virtio-scsi: Move DEFINE_VIRTIO_SCSI_FEATURES to virtio-scsi shannon.zhao
2015-04-28 0:32 ` Shannon Zhao
2015-04-28 5:55 ` Michael S. Tsirkin [this message]
2015-04-28 6:30 ` Shannon Zhao
2015-04-28 7:15 ` Michael S. Tsirkin
2015-04-28 7:28 ` Shannon Zhao
2015-04-28 8:18 ` Michael S. Tsirkin
2015-04-28 9:29 ` Peter Maydell
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=20150428075441-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=cornelia.huck@de.ibm.com \
--cc=hangaohuai@huawei.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.org \
--cc=zhaoshenglong@huawei.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;
as well as URLs for NNTP newsgroup(s).