From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com,
Akio Takebe <takebe_akio@jp.fujitsu.com>,
xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: Re: [Patch] cleanup warning in xen/ia64
Date: Mon, 27 Feb 2006 16:32:42 +0900 [thread overview]
Message-ID: <9C63B6FFEC607takebe_akio@jp.fujitsu.com> (raw)
In-Reply-To: <8ff8162553b06b9ebf657294ce260390@cl.cam.ac.uk>
[-- Attachment #1: Mail message body --]
[-- Type: text/plain, Size: 858 bytes --]
Hi, Keir
>For xen (common)
> - cleanup.include.xen.patch
Yes, this work is for Xen/ia64.
This patch isn't concerned with Xen/x86.
But strlcpy() is in xen/common/string.c,
so I think strlcpy() should be defined in xen/include/xen/string.h.
Otherwise should strlcpy() be defined in xen/include/asm-ia64/linux/asm/
string.h?
Best Regards,
Akio Takebe
>
>On 27 Feb 2006, at 01:48, Akio Takebe wrote:
>
>> We clean up warning in xen/ia64 .
>> We have cleaned up many warnings, but it remainded some warnings yet.
>>
>> These patches fix many issue (ex. panic dom0, oops domU/dom0...).
>> we will fix compile warnnings one step at a time.
>
>I'll assume these are destined for the ia64-unstable tree.
>
> -- Keir
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
[-- Attachment #2: cleanup.include.xen.patch --]
[-- Type: application/octet-stream, Size: 455 bytes --]
diff -r 6c43118bdba8 xen/include/xen/string.h
--- a/xen/include/xen/string.h Fri Feb 24 22:41:08 2006
+++ b/xen/include/xen/string.h Sun Feb 26 16:53:57 2006
@@ -24,6 +24,9 @@
#endif
#ifndef __HAVE_ARCH_STRNCPY
extern char * strncpy(char *,const char *, __kernel_size_t);
+#endif
+#ifndef __HAVE_ARCH_STRLCPY
+extern size_t strlcpy(char *,const char *, __kernel_size_t);
#endif
#ifndef __HAVE_ARCH_STRCAT
extern char * strcat(char *, const char *);
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-02-27 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 1:48 [Patch] cleanup warning in xen/ia64 Akio Takebe
2006-02-27 7:02 ` Keir Fraser
2006-02-27 7:32 ` Akio Takebe [this message]
2006-02-27 7:38 ` Keir Fraser
2006-02-27 16:44 ` [Xen-ia64-devel] " Alex Williamson
2006-02-28 4:15 ` [Xen-ia64-devel] [Patch] [RESEND] " Masaki Kanno
2006-02-28 18:34 ` Alex Williamson
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=9C63B6FFEC607takebe_akio@jp.fujitsu.com \
--to=takebe_akio@jp.fujitsu.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-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.