From: Avi Kivity <avi@qumranet.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, kvm-devel@lists.sourceforge.net,
tglx <tglx@linutronix.de>, mingo <mingo@redhat.com>,
hpa <hpa@zytor.com>
Subject: Re: [PATCH] x86: kvmclock needs to include apic.h
Date: Sun, 16 Mar 2008 13:11:08 +0200 [thread overview]
Message-ID: <47DD004C.7010108@qumranet.com> (raw)
In-Reply-To: <20080314112457.a7bc2358.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> kvmclock needs to #include apic.h to prevent a build error:
>
> next-20080314/arch/x86/kernel/kvmclock.c:142: error: implicit declaration of function 'setup_secondary_APIC_clock'
> elan1.out:make[2]: *** [arch/x86/kernel/kvmclock.o] Error 1
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-03-16 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 18:24 [PATCH] x86: kvmclock needs to include apic.h Randy Dunlap
2008-03-16 11:11 ` Avi Kivity [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=47DD004C.7010108@qumranet.com \
--to=avi@qumranet.com \
--cc=hpa@zytor.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=randy.dunlap@oracle.com \
--cc=tglx@linutronix.de \
/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