From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: cornelia.huck@de.ibm.com, kwolf@redhat.com, pbonzini@redhat.com,
stefanha@redhat.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH v4 6/6] virtio-scsi: Replace HandleOutput typedef
Date: Wed, 13 Jul 2016 13:09:48 +0800 [thread overview]
Message-ID: <1468386588-26584-7-git-send-email-famz@redhat.com> (raw)
In-Reply-To: <1468386588-26584-1-git-send-email-famz@redhat.com>
There is a new common one in virtio.h, use it.
Signed-off-by: Fam Zheng <famz@redhat.com>
---
hw/scsi/virtio-scsi.c | 5 +++--
include/hw/virtio/virtio-scsi.h | 6 ++----
2 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virtio-scsi.c
index 45e2ee8..88d4bf0 100644
--- a/hw/scsi/virtio-scsi.c
+++ b/hw/scsi/virtio-scsi.c
@@ -824,8 +824,9 @@ static struct SCSIBusInfo virtio_scsi_scsi_info = {
};
void virtio_scsi_common_realize(DeviceState *dev, Error **errp,
- HandleOutput ctrl, HandleOutput evt,
- HandleOutput cmd)
+ VirtIOHandleOutput ctrl,
+ VirtIOHandleOutput evt,
+ VirtIOHandleOutput cmd)
{
VirtIODevice *vdev = VIRTIO_DEVICE(dev);
VirtIOSCSICommon *s = VIRTIO_SCSI_COMMON(dev);
diff --git a/include/hw/virtio/virtio-scsi.h b/include/hw/virtio/virtio-scsi.h
index 5e3f088..a1e0cfb 100644
--- a/include/hw/virtio/virtio-scsi.h
+++ b/include/hw/virtio/virtio-scsi.h
@@ -121,11 +121,9 @@ typedef struct VirtIOSCSIReq {
} req;
} VirtIOSCSIReq;
-typedef void (*HandleOutput)(VirtIODevice *, VirtQueue *);
-
void virtio_scsi_common_realize(DeviceState *dev, Error **errp,
- HandleOutput ctrl, HandleOutput evt,
- HandleOutput cmd);
+ VirtIOHandleOutput ctrl, VirtIOHandleOutput evt,
+ VirtIOHandleOutput cmd);
void virtio_scsi_common_unrealize(DeviceState *dev, Error **errp);
void virtio_scsi_handle_event_vq(VirtIOSCSI *s, VirtQueue *vq);
--
2.7.4
next prev parent reply other threads:[~2016-07-13 5:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 5:09 [Qemu-devel] [PATCH v4 0/6] virtio: Merge virtio-{blk, scsi} host notifier handling paths Fam Zheng
2016-07-13 5:09 ` [Qemu-devel] [PATCH v4 1/6] virtio: Add typedef for handle_output Fam Zheng
2016-07-13 9:03 ` Cornelia Huck
2016-07-13 5:09 ` [Qemu-devel] [PATCH v4 2/6] virtio: Introduce virtio_add_queue_aio Fam Zheng
2016-07-13 9:07 ` Cornelia Huck
2016-07-13 5:09 ` [Qemu-devel] [PATCH v4 3/6] virtio-blk: Call virtio_add_queue_aio Fam Zheng
2016-07-13 9:09 ` Cornelia Huck
2016-07-13 5:09 ` [Qemu-devel] [PATCH v4 4/6] virtio-scsi: " Fam Zheng
2016-07-13 9:09 ` Cornelia Huck
2016-07-13 5:09 ` [Qemu-devel] [PATCH v4 5/6] Revert "mirror: Workaround for unexpected iohandler events during completion" Fam Zheng
2016-07-13 9:10 ` Cornelia Huck
2016-07-13 5:09 ` Fam Zheng [this message]
2016-07-13 9:11 ` [Qemu-devel] [PATCH v4 6/6] virtio-scsi: Replace HandleOutput typedef Cornelia Huck
2016-07-13 9:00 ` [Qemu-devel] [PATCH v4 0/6] virtio: Merge virtio-{blk, scsi} host notifier handling paths Cornelia Huck
2016-07-13 10:32 ` Paolo Bonzini
2016-07-14 12:18 ` Stefan Hajnoczi
2016-07-14 12:18 ` 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=1468386588-26584-7-git-send-email-famz@redhat.com \
--to=famz@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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 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).