From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] Trace: add __print_symbolic_u64 to avoid warnings on 32bit machine Date: Fri, 15 Apr 2011 12:37:46 -0400 Message-ID: <20110415163746.GA14185@infradead.org> References: <4D9573DB.4010009@cn.fujitsu.com> <1301665762.2160.22.camel@gandalf.stny.rr.com> <4D9C2FF6.7090607@cn.fujitsu.com> <20110415092418.b18fd6fe.randy.dunlap@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: liubo , Steven Rostedt , Linux Btrfs , Linux Kernel Mailing List , Chris Mason To: Randy Dunlap Return-path: In-Reply-To: <20110415092418.b18fd6fe.randy.dunlap@oracle.com> List-ID: On Fri, Apr 15, 2011 at 09:24:18AM -0700, Randy Dunlap wrote: > Can this also be used to stop this warning that has been around > like forever (on i386)? > > linux-next-20110415/fs/xfs/linux-2.6/./xfs_trace.h:1354: warning: format '%llx' expects type 'long long unsigned int', but argument 22 has type 'xfs_fsblock_t' What about reporting the bug? And no, it won't help. The only thing that helps would be casting the argument to (long long). If you send me (and/or the xfs list) a list of the warnings you see I'm happy to fix them, although I don't see them during my x86 builds. Could it be that you have CONFIG_LBD disabled? That's surely not a popular option with XFS users.