* Randy Dunlap <randy.dunlap@oracle.com> wrote:
quoted text > Fix printk formats in x86/mm/ioremap.c:
>
> next-20080410/arch/x86/mm/ioremap.c:137: warning: format '%llx' expects type 'long long unsigned int', but argument 2 has type 'resource_size_t'
> next-20080410/arch/x86/mm/ioremap.c:188: warning: format '%llx' expects type 'long long unsigned int', but argument 2 has type 'resource_size_t'
> next-20080410/arch/x86/mm/ioremap.c:188: warning: format '%llx' expects type 'long long unsigned int', but argument 3 has type 'long unsigned int'
thanks, applied.
quoted text > if (!phys_addr_valid(phys_addr)) {
> printk(KERN_WARNING "ioremap: invalid physical address %llx\n",
> - phys_addr);
> + (unsigned long long)phys_addr);
is there really no way to solve this more cleanly than a forced cast? It
is a totally uninteresting warning that we pass in a narrower type to
printk(). It cannot ever cause any bugs or problems. Why does gcc warn
about it?
Ingo
--
unsubscribe notice To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Messages in current thread:
Re: linux-next: Tree for April 10 (arch/x86) , Ingo Molnar , (Fri Apr 11, 12:46 am)