From: Jan Kara <jack@suse•cz>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Mark Fasheh <mfasheh@suse•com>, linux-next@vger•kernel.org
Subject: Re: linux-next: ocsf2 tree build warnings
Date: Tue, 25 Nov 2008 14:16:56 +0100 [thread overview]
Message-ID: <20081125131656.GC460@duck.suse.cz> (raw)
In-Reply-To: <20081125213102.28efa104.sfr@canb.auug.org.au>
On Tue 25-11-08 21:31:02, Stephen Rothwell wrote:
> Hi Mark,
>
> Today's linux-next build (powerpc allyesconfig) produced these warnings:
Thanks, these slipped my attention. Fixed.
> fs/ocfs2/quota_local.c: In function 'olq_set_dquot':
> fs/ocfs2/quota_local.c:844: warning: format '%lld' expects type 'long long int', but argument 7 has type '__le64'
> fs/ocfs2/quota_local.c:844: warning: format '%lld' expects type 'long long int', but argument 8 has type '__le64'
> fs/ocfs2/quota_local.c:844: warning: format '%lld' expects type 'long long int', but argument 7 has type '__le64'
> fs/ocfs2/quota_local.c:844: warning: format '%lld' expects type 'long long int', but argument 8 has type '__le64'
> fs/ocfs2/quota_local.c:844: warning: format '%lld' expects type 'long long int', but argument 7 has type '__le64'
> fs/ocfs2/quota_local.c:844: warning: format '%lld' expects type 'long long int', but argument 8 has type '__le64'
> fs/ocfs2/quota_global.c: In function '__ocfs2_sync_dquot':
> fs/ocfs2/quota_global.c:457: warning: format '%lld' expects type 'long long int', but argument 8 has type 's64'
> fs/ocfs2/quota_global.c:457: warning: format '%lld' expects type 'long long int', but argument 10 has type 's64'
> fs/ocfs2/quota_global.c:457: warning: format '%lld' expects type 'long long int', but argument 8 has type 's64'
> fs/ocfs2/quota_global.c:457: warning: format '%lld' expects type 'long long int', but argument 10 has type 's64'
> fs/ocfs2/quota_global.c:457: warning: format '%lld' expects type 'long long int', but argument 8 has type 's64'
> fs/ocfs2/quota_global.c:457: warning: format '%lld' expects type 'long long int', but argument 10 has type 's64'
>
> These are because s64 is "long" on some architectures. Our usual
> solution is to cast them to "long long" when printing them. Also, you
> shouldn't directly print an __le64 (you need to convert it to the host
> type first for it to make much sense.
Honza
--
Jan Kara <jack@suse•cz>
SUSE Labs, CR
prev parent reply other threads:[~2008-11-25 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 10:31 linux-next: ocsf2 tree build warnings Stephen Rothwell
2008-11-25 13:16 ` Jan Kara [this message]
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=20081125131656.GC460@duck.suse.cz \
--to=jack@suse$(echo .)cz \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mfasheh@suse$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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