From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH]xl: Some small fixes to xl Date: Mon, 24 May 2010 10:32:59 -0700 Message-ID: <4BFAB84B.7010400@goop.org> References: <4BF62FB9.40008@cn.fujitsu.com> <4BF6DE1D.6070904@goop.org> <4BF9CCEE.9010300@cn.fujitsu.com> <19450.21443.778306.286619@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: Yang Hongyang , Ian Jackson , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 05/24/2010 03:31 AM, Stefano Stabellini wrote: > On Mon, 24 May 2010, Ian Jackson wrote: > >> Stefano Stabellini writes ("Re: [Xen-devel] [PATCH]xl: Some small fixes to xl"): >> >>> Finally in the printf call the best way to print a uint64_t in decimal >>> format is using PRId64. >>> >> PRIu64 I think you mean. PRId64 is for int64_t. >> > > Yes, thank you > I personally find those format macros pretty odious and avoid them unless there's no other option, but I'll leave that up to you. J