From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Jianjun Kong <jianjun@zeuux.org>
Cc: mingo@elte.hu, Linux-Kernel-Mailing-List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arch/x86: Fix waring when build on x86_32
Date: Fri, 17 Oct 2008 12:30:10 +0100 [thread overview]
Message-ID: <20081017113010.GD2951@hack.voiplan.pt> (raw)
In-Reply-To: <20081017111829.GA20328@ubuntu>
On Fri, Oct 17, 2008 at 07:18:29PM +0800, Jianjun Kong wrote:
>
>Fix the waring When I buile the Linux-2.6 kernel on x86_32.
>arch/x86/kernel/io_apic_32.c: In function 'print_local_APIC':
>arch/x86/kernel/io_apic_32.c:1539: warning: format '%08x' expects type 'unsigned int', but argument 2 has type 'u64'
>arch/x86/kernel/io_apic_32.c:1540: warning: format '%08x' expects type 'unsigned int', but argument 2 has type 'u64'
>
>Signed-off-by: Jianjun Kong <jianjun@zeuux.org>
>---
> arch/x86/kernel/io_apic_32.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/arch/x86/kernel/io_apic_32.c b/arch/x86/kernel/io_apic_32.c
>index e710289..f678d12 100644
>--- a/arch/x86/kernel/io_apic_32.c
>+++ b/arch/x86/kernel/io_apic_32.c
>@@ -1536,8 +1536,8 @@ __apicdebuginit(void) print_local_APIC(void *dummy)
> }
>
> icr = apic_icr_read();
>- printk(KERN_DEBUG "... APIC ICR: %08x\n", icr);
>- printk(KERN_DEBUG "... APIC ICR2: %08x\n", icr >> 32);
>+ printk(KERN_DEBUG "... APIC ICR: %08x\n", (unsigned int)icr);
>+ printk(KERN_DEBUG "... APIC ICR2: %08x\n", (unsigned int)(icr >> 32));
>
http://lkml.org/lkml/2008/8/19/566
http://lkml.org/lkml/2008/8/20/119
--
"Sometimes the only way to stay sane is to go a little crazy."
prev parent reply other threads:[~2008-10-17 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 11:18 [PATCH] arch/x86: Fix waring when build on x86_32 Jianjun Kong
2008-10-17 11:30 ` Américo Wang [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=20081017113010.GD2951@hack.voiplan.pt \
--to=xiyou.wangcong@gmail.com \
--cc=jianjun@zeuux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.