From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com
Subject: [Qemu-devel] [PATCH 1.1] declare ECANCELED on all machines
Date: Thu, 10 May 2012 09:27:50 +0200 [thread overview]
Message-ID: <1336634870-4257-1-git-send-email-pbonzini@redhat.com> (raw)
This is needed in particular on Win32.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
Kevin, this fixes the failure to build block branch on mingw.
qemu-common.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/qemu-common.h b/qemu-common.h
index 50f659a..cccfb42 100644
--- a/qemu-common.h
+++ b/qemu-common.h
@@ -61,6 +61,9 @@ typedef struct Monitor Monitor;
#if !defined(ENOTSUP)
#define ENOTSUP 4096
#endif
+#if !defined(ECANCELED)
+#define ECANCELED 4097
+#endif
#ifndef TIME_MAX
#define TIME_MAX LONG_MAX
#endif
--
1.7.10.1
next reply other threads:[~2012-05-10 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 7:27 Paolo Bonzini [this message]
2012-05-10 8:20 ` [Qemu-devel] [PATCH 1.1] declare ECANCELED on all machines Kevin Wolf
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=1336634870-4257-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).