From: Meelis Roos <mroos@linux.ee>
To: Linux Kernel list <linux-kernel@vger.kernel.org>,
joel.becker@oracle.com, mfasheh@suse.com
Subject: OCFS2 printf format warnings
Date: Sun, 18 May 2008 16:59:26 +0300 (EEST) [thread overview]
Message-ID: <Pine.SOC.4.64.0805181658030.22653@math.ut.ee> (raw)
Just noticed these on sparc64:
CC [M] fs/ocfs2/cluster/netdebug.o
fs/ocfs2/cluster/netdebug.c: In function 'nst_seq_show':
fs/ocfs2/cluster/netdebug.c:152: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'suseconds_t'
fs/ocfs2/cluster/netdebug.c:152: warning: format '%lu' expects type 'long unsigned int', but argument 15 has type 'suseconds_t'
fs/ocfs2/cluster/netdebug.c:152: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'suseconds_t'
fs/ocfs2/cluster/netdebug.c: In function 'sc_seq_show':
fs/ocfs2/cluster/netdebug.c:332: warning: format '%lu' expects type 'long unsigned int', but argument 19 has type 'suseconds_t'
fs/ocfs2/cluster/netdebug.c:332: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'suseconds_t'
fs/ocfs2/cluster/netdebug.c:332: warning: format '%lu' expects type 'long unsigned int', but argument 23 has type 'suseconds_t'
fs/ocfs2/cluster/netdebug.c:332: warning: format '%lu' expects type 'long unsigned int', but argument 25 has type 'suseconds_t'
fs/ocfs2/cluster/netdebug.c:332: warning: format '%lu' expects type 'long unsigned int', but argument 27 has type 'suseconds_t'
fs/ocfs2/cluster/netdebug.c:332: warning: format '%lu' expects type 'long unsigned int', but argument 29 has type 'suseconds_t'
--
Meelis Roos (mroos@linux.ee)
next reply other threads:[~2008-05-18 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 13:59 Meelis Roos [this message]
2008-05-19 19:07 ` Mark Fasheh
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=Pine.SOC.4.64.0805181658030.22653@math.ut.ee \
--to=mroos@linux.ee \
--cc=joel.becker@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.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
all inboxes | Powered by JetHome®