From: Christoph Egger <Christoph.Egger@amd.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: [PATCH] fix build error w/o MEMSHR
Date: Fri, 13 Apr 2012 16:25:00 +0200 [thread overview]
Message-ID: <4F88373C.6050007@amd.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 154 bytes --]
Do not include memshr.h when MEMSHR is not defined.
Fixes build error when MEMSHR is disabled.
Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
[-- Attachment #2: xen_tools_blktapctrl.diff --]
[-- Type: text/plain, Size: 438 bytes --]
diff -r ab552da976a3 tools/blktap/drivers/blktapctrl.c
--- a/tools/blktap/drivers/blktapctrl.c Wed Apr 11 18:28:33 2012 +0200
+++ b/tools/blktap/drivers/blktapctrl.c Fri Apr 13 16:21:11 2012 +0200
@@ -50,7 +50,9 @@
#include <xs.h>
#include <sys/time.h>
#include <syslog.h>
+#ifdef MEMSHR
#include <memshr.h>
+#endif
#include <sys/stat.h>
#include "blktaplib.h"
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2012-04-13 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 14:25 Christoph Egger [this message]
2012-04-24 17:16 ` [PATCH] fix build error w/o MEMSHR Ian Jackson
2012-04-25 9:09 ` Christoph Egger
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=4F88373C.6050007@amd.com \
--to=christoph.egger@amd.com \
--cc=xen-devel@lists.xen.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).