From mboxrd@z Thu Jan 1 00:00:00 1970 From: Akio Takebe Subject: Re: [Patch] cleanup warning in xen/ia64 Date: Mon, 27 Feb 2006 16:32:42 +0900 Message-ID: <9C63B6FFEC607takebe_akio@jp.fujitsu.com> References: <8ff8162553b06b9ebf657294ce260390@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Boundary-v3MlPSdg975FmodTUbfXM" Return-path: In-Reply-To: <8ff8162553b06b9ebf657294ce260390@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com, Akio Takebe , xen-ia64-devel List-Id: xen-devel@lists.xenproject.org --Boundary-v3MlPSdg975FmodTUbfXM Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Content-Description: Mail message body 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 --Boundary-v3MlPSdg975FmodTUbfXM Content-Type: application/octet-stream; name="cleanup.include.xen.patch" Content-Disposition: attachment; filename="cleanup.include.xen.patch" Content-Transfer-Encoding: base64 ZGlmZiAtciA2YzQzMTE4YmRiYTggeGVuL2luY2x1ZGUveGVuL3N0cmluZy5oCi0tLSBhL3hl bi9pbmNsdWRlL3hlbi9zdHJpbmcuaAlGcmkgRmViIDI0IDIyOjQxOjA4IDIwMDYKKysrIGIv eGVuL2luY2x1ZGUveGVuL3N0cmluZy5oCVN1biBGZWIgMjYgMTY6NTM6NTcgMjAwNgpAQCAt MjQsNiArMjQsOSBAQAogI2VuZGlmCiAjaWZuZGVmIF9fSEFWRV9BUkNIX1NUUk5DUFkKIGV4 dGVybiBjaGFyICogc3RybmNweShjaGFyICosY29uc3QgY2hhciAqLCBfX2tlcm5lbF9zaXpl X3QpOworI2VuZGlmCisjaWZuZGVmIF9fSEFWRV9BUkNIX1NUUkxDUFkKK2V4dGVybiBzaXpl X3Qgc3RybGNweShjaGFyICosY29uc3QgY2hhciAqLCBfX2tlcm5lbF9zaXplX3QpOwogI2Vu ZGlmCiAjaWZuZGVmIF9fSEFWRV9BUkNIX1NUUkNBVAogZXh0ZXJuIGNoYXIgKiBzdHJjYXQo Y2hhciAqLCBjb25zdCBjaGFyICopOwo= --Boundary-v3MlPSdg975FmodTUbfXM Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --Boundary-v3MlPSdg975FmodTUbfXM--