From: Ingo Molnar <mingo@kernel.org>
To: Gleb Natapov <gleb@redhat.com>
Cc: Shuah Khan <shuah.khan@hp.com>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
avi@redhat.com, mtosatti@redhat.com, mst@redhat.com,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, shuahkhan@gmail.com
Subject: Re: [PATCH linux-next] x86/kvm: Fix compile warning in kvm_register_steal_time()
Date: Mon, 11 Feb 2013 11:06:56 +0100 [thread overview]
Message-ID: <20130211100656.GA4560@gmail.com> (raw)
In-Reply-To: <20130211100439.GH23932@gmail.com>
* Ingo Molnar <mingo@kernel.org> wrote:
>
> * Gleb Natapov <gleb@redhat.com> wrote:
>
> > On Tue, Feb 05, 2013 at 07:57:22PM -0700, Shuah Khan wrote:
> > > Fix the following compile warning in kvm_register_steal_time():
> > > CC arch/x86/kernel/kvm.o
> > > arch/x86/kernel/kvm.c: In function ?kvm_register_steal_time?:
> > > arch/x86/kernel/kvm.c:302:3: warning: format ?%lx? expects argument of type ?long unsigned int?, but argument 3 has type ?phys_addr_t? [-Wformat]
> > >
> > Ingo, the warning is from the tip tree. Can you take the fix?
>
> Yeah, it came via these x86 improvements to __pa():
>
> 5dfd486c4750 x86, kvm: Fix kvm's use of __pa() on percpu areas
> d76565344512 x86, mm: Create slow_virt_to_phys()
> f3c4fbb68e93 x86, mm: Use new pagetable helpers in try_preserve_large_page()
> 4cbeb51b860c x86, mm: Pagetable level size/shift/mask helpers
> a25b9316841c x86, mm: Make DEBUG_VIRTUAL work earlier in boot
>
> So up the fix - I added an Acked-by from you as well, is that
s/So I applied the fix
Thanks,
Ingo
next prev parent reply other threads:[~2013-02-11 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 2:57 [PATCH linux-next] x86/kvm: Fix compile warning in kvm_register_steal_time() Shuah Khan
2013-02-11 9:06 ` Gleb Natapov
2013-02-11 10:04 ` Ingo Molnar
2013-02-11 10:05 ` Gleb Natapov
2013-02-11 10:06 ` Ingo Molnar [this message]
2013-02-11 12:36 ` [tip:x86/mm] " tip-bot for Shuah Khan
2013-02-13 14:35 ` Borislav Petkov
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=20130211100656.GA4560@gmail.com \
--to=mingo@kernel.org \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=shuah.khan@hp.com \
--cc=shuahkhan@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 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.