From: Reiner Sailer <sailer@us.ibm.com>
To: xen-devel@lists.xensource.com
Cc: Steven Hand <Steven.Hand@cl.cam.ac.uk>
Subject: [BUGFIX][ACM] fix build break by adding missing paranthesis after cleanup
Date: Wed, 23 Aug 2006 18:06:12 -0400 [thread overview]
Message-ID: <44ECD154.8020902@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 175 bytes --]
This small patch adds back a closing paranthesis that has gone lost. It
fixes the build for the Xen access control module.
Signed-off by: Reiner Sailer <sailer@us.ibm.com>
[-- Attachment #2: acm_cleanup_fix.diff --]
[-- Type: text/plain, Size: 712 bytes --]
Index: xen-unstable.hg-shype/xen/acm/acm_simple_type_enforcement_hooks.c
===================================================================
--- xen-unstable.hg-shype.orig/xen/acm/acm_simple_type_enforcement_hooks.c
+++ xen-unstable.hg-shype/xen/acm/acm_simple_type_enforcement_hooks.c
@@ -353,7 +353,7 @@ ste_dump_stats(u8 *buf, u16 buf_len)
stats.ec_cachehit_count = htonl(atomic_read(&ste_bin_pol.ec_cachehit_count));
stats.gt_cachehit_count = htonl(atomic_read(&ste_bin_pol.gt_cachehit_count));
- if (buf_len < sizeof(struct acm_ste_stats_buffer)
+ if (buf_len < sizeof(struct acm_ste_stats_buffer))
return -ENOMEM;
memcpy(buf, &stats, sizeof(struct acm_ste_stats_buffer));
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2006-08-23 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 22:06 Reiner Sailer [this message]
2006-08-23 22:14 ` [BUGFIX][ACM] fix build break by adding missing paranthesis after cleanup Ewan Mellor
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=44ECD154.8020902@us.ibm.com \
--to=sailer@us.ibm.com \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.