From: "L. A. Walsh" <lkml@tlinx.org>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Cc: Linux-Xfs <linux-xfs@oss.sgi.com>
Subject: Compile warnings in XFS, kernel 2.6.15.1
Date: Mon, 30 Jan 2006 19:19:23 -0800 [thread overview]
Message-ID: <43DED73B.7060902@tlinx.org> (raw)
Are these warnings anything to worry about?
CC fs/xfs/xfs_bmap.o
LD fs/udf/udf.o
LD fs/udf/built-in.o
CC fs/dnotify.o
CC fs/xfs/xfs_bmap_btree.o
fs/xfs/xfs_bmap.c: In function `xfs_bmap_search_extents':
fs/xfs/xfs_bmap.c:3590: warning: long long unsigned int format,
different type arg (arg 5)
CC fs/xfs/xfs_btree.o
CC fs/xfs/xfs_buf_item.o
CC fs/xfs/xfs_iget.o
CC fs/xfs/xfs_inode.o
CC fs/xfs/xfs_inode_item.o
CC fs/xfs/xfs_iocore.o
CC fs/xfs/xfs_iomap.o
CC fs/xfs/xfs_itable.o
fs/xfs/xfs_iomap.c: In function `xfs_iomap_write_direct':
fs/xfs/xfs_iomap.c:488: warning: long long unsigned int format,
different type arg (arg 5)
fs/xfs/xfs_iomap.c: In function `xfs_iomap_write_delay':
fs/xfs/xfs_iomap.c:591: warning: long long unsigned int format,
different type arg (arg 5)
fs/xfs/xfs_iomap.c:697: warning: long long unsigned int format,
different type arg (arg 5)
fs/xfs/xfs_iomap.c: In function `xfs_iomap_write_allocate':
fs/xfs/xfs_iomap.c:834: warning: long long unsigned int format,
different type arg (arg 5)
fs/xfs/xfs_iomap.c: In function `xfs_iomap_write_unwritten':
fs/xfs/xfs_iomap.c:941: warning: long long unsigned int format,
different type arg (arg 5)
next reply other threads:[~2006-01-31 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 3:19 L. A. Walsh [this message]
2006-01-31 4:53 ` Compile warnings in XFS, kernel 2.6.15.1 Nathan Scott
2006-02-01 0:24 ` John Klingler
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=43DED73B.7060902@tlinx.org \
--to=lkml@tlinx.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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 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.