WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-changelog

[Xen-changelog] [xen-unstable] [powerpc] xencomm: print function names s

To: xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-changelog] [xen-unstable] [powerpc] xencomm: print function names so we can tell which one failed
From: Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Fri, 28 Jul 2006 16:21:52 +0000
Delivery-date: Fri, 28 Jul 2006 09:32:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-changelog-request@lists.xensource.com?subject=help>
List-id: BK change log <xen-changelog.lists.xensource.com>
List-post: <mailto:xen-changelog@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-changelog-bounces@xxxxxxxxxxxxxxxxxxx
# HG changeset patch
# User Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
# Node ID fcef9a741e1dcd07a740218d393441a5985cafc5
# Parent  b8ec4423cc4413aea5e586813b2e20075466108e
[powerpc] xencomm: print function names so we can tell which one failed

Signed-off-by: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
---
 xen/arch/powerpc/usercopy.c |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

diff -r b8ec4423cc44 -r fcef9a741e1d xen/arch/powerpc/usercopy.c
--- a/xen/arch/powerpc/usercopy.c       Thu Jul 27 11:12:04 2006 +0100
+++ b/xen/arch/powerpc/usercopy.c       Thu Jul 13 11:25:36 2006 -0400
@@ -86,7 +86,8 @@ xencomm_copy_from_guest(void *to, const 
     /* first we need to access the descriptor */
     desc = (struct xencomm_desc *)paddr_to_maddr((unsigned long)from);
     if (desc->magic != XENCOMM_MAGIC) {
-        printk("xencomm error: %p magic was 0x%x\n", desc, desc->magic);
+        printk("%s: error: %p magic was 0x%x\n",
+               __func__, desc, desc->magic);
         return n;
     }
 
@@ -153,7 +154,7 @@ xencomm_copy_to_guest(void *to, const vo
     /* first we need to access the descriptor */
     desc = (struct xencomm_desc *)paddr_to_maddr((unsigned long)to);
     if (desc->magic != XENCOMM_MAGIC) {
-        printk("xencomm error: %p magic was 0x%x\n", desc, desc->magic);
+        printk("%s error: %p magic was 0x%x\n", __func__, desc, desc->magic);
         return n;
     }
 
@@ -206,7 +207,7 @@ void xencomm_add_offset(void *handle, un
     /* first we need to access the descriptor */
     desc = (struct xencomm_desc *)paddr_to_maddr((unsigned long)handle);
     if (desc->magic != XENCOMM_MAGIC) {
-        printk("xencomm error: %p magic was 0x%x\n", desc, desc->magic);
+        printk("%s error: %p magic was 0x%x\n", __func__, desc, desc->magic);
         return;
     }
 

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-changelog] [xen-unstable] [powerpc] xencomm: print function names so we can tell which one failed, Xen patchbot-unstable <=