From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Weil <weil@mail.berlios.de>,
Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 1/2] aio-win32: replace incorrect AioHandler->opaque usage with ->e
Date: Thu, 22 Aug 2013 15:28:35 +0200 [thread overview]
Message-ID: <1377178116-28488-2-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1377178116-28488-1-git-send-email-stefanha@redhat.com>
The AioHandler->opaque field does not exist in aio-win32.c. The code
that uses it was incorrectly copied from aio-posix.c. For Windows we
can use AioHandler->e to match against AioContext->notifier.
This patch fixes the Windows build for aio-win32.o.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
aio-win32.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/aio-win32.c b/aio-win32.c
index 78b2801..efb2d5a 100644
--- a/aio-win32.c
+++ b/aio-win32.c
@@ -125,7 +125,7 @@ bool aio_poll(AioContext *ctx, bool blocking)
node->io_notify(node->e);
/* aio_notify() does not count as progress */
- if (node->opaque != &ctx->notifier) {
+ if (node->e != &ctx->notifier) {
progress = true;
}
}
@@ -188,7 +188,7 @@ bool aio_poll(AioContext *ctx, bool blocking)
node->io_notify(node->e);
/* aio_notify() does not count as progress */
- if (node->opaque != &ctx->notifier) {
+ if (node->e != &ctx->notifier) {
progress = true;
}
}
--
1.8.3.1
next prev parent reply other threads:[~2013-08-22 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 13:28 [Qemu-devel] [PATCH 0/2] win32: build fixes due to io_flush removal Stefan Hajnoczi
2013-08-22 13:28 ` Stefan Hajnoczi [this message]
2013-08-22 13:28 ` [Qemu-devel] [PATCH 2/2] win32-aio: drop win32_aio_flush_cb() Stefan Hajnoczi
2013-08-22 14:33 ` [Qemu-devel] [PATCH 0/2] win32: build fixes due to io_flush removal Stefan Weil
2013-08-22 20:05 ` 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=1377178116-28488-2-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).