From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Chinner <david@fromorbit.com>, xfs-masters@oss.sgi.com
Cc: linux-next@vger.kernel.org
Subject: linux-next: xfs tree build warnings
Date: Mon, 29 Dec 2008 19:26:49 +1100 [thread overview]
Message-ID: <20081229192649.7099188b.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]
Hi David,
Today's linux-next build (powerpc ppc64_defconfig) failed like this:
fs/xfs/xfs_inode.c: In function 'xfs_iflush_int':
fs/xfs/xfs_inode.c:3055: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_inode.c:3062: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_inode.c:3072: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_inode.c:3083: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_inode.c:3095: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_inode.c:3102: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c: In function 'xlog_recover_do_inode_trans':
fs/xfs/xfs_log_recover.c:2300: warning: format '%Ld' expects type 'long long int', but argument 6 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c:2311: warning: format '%Ld' expects type 'long long int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c:2344: warning: format '%Ld' expects type 'long long int', but argument 7 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c:2357: warning: format '%Ld' expects type 'long long int', but argument 7 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c:2370: warning: format '%Ld' expects type 'long long int', but argument 7 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c:2380: warning: format '%Ld' expects type 'long long int', but argument 7 has type 'xfs_ino_t'
I am just flagging these to be consistent. Ingo will probably say
something about u64 and unsigned long long vs. unsigned long ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-12-29 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 8:26 Stephen Rothwell [this message]
2008-12-29 8:36 ` [xfs-masters] linux-next: xfs tree build warnings Christoph Hellwig
2008-12-29 8:51 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-06-12 1:46 Stephen Rothwell
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=20081229192649.7099188b.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=david@fromorbit.com \
--cc=linux-next@vger.kernel.org \
--cc=xfs-masters@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox