From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: Build warning in todays linus/master
Date: Mon, 21 Mar 2011 11:01:05 +0000 [thread overview]
Message-ID: <20110321110105.GB2610@pulham.picochip.com> (raw)
Hi Will,
I'm getting a build warning on todays master build for my V6K platform:
CC arch/arm/mm/mmu.o
arch/arm/mm/mmu.c: In function 'create_36bit_mapping':
arch/arm/mm/mmu.c:601:10: warning: format '%08llx' expects type 'long long unsigned int', but argument 2 has type 'unsigned int'
arch/arm/mm/mmu.c:614:10: warning: format '%08llx' expects type 'long long unsigned int', but argument 2 has type 'unsigned int'
arch/arm/mm/mmu.c:621:10: warning: format '%08llx' expects type 'long long unsigned int', but argument 2 has type 'unsigned int'
arch/arm/mm/mmu.c: In function 'create_mapping':
arch/arm/mm/mmu.c:662:10: warning: format '%08llx' expects type 'long long unsigned int', but argument 2 has type 'unsigned int'
arch/arm/mm/mmu.c:670:10: warning: format '%08llx' expects type 'long long unsigned int', but argument 2 has type 'unsigned int'
arch/arm/mm/mmu.c:690:10: warning: format '%08lx' expects type 'long unsigned int', but argument 2 has type 'unsigned int'
Which is introduced by (3a6b16 [ARM: 6675/1: use phys_addr_t instead of
unsigned long in conversion code]), because phys_addr_t is a u32
(!CONFIG_PHYS_ADDR_T_64BIT). I guess a cast to u64 in the printk()'s in
arch/arm/mm/mmu.c would fix these up, is that the right approach?
Jamie
next reply other threads:[~2011-03-21 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 11:01 Jamie Iles [this message]
2011-03-21 11:40 ` Build warning in todays linus/master Will Deacon
2011-03-21 11:50 ` Jamie Iles
2011-03-21 11:58 ` Russell King - ARM Linux
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=20110321110105.GB2610@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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