From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org, alexey.eremenko@qumranet.com, jan.kiszka@web.de
Subject: Re: [PATCH] [RESEND] Make KVM compile on split source/object kernel configurations
Date: Tue, 07 Oct 2008 16:42:56 +0200 [thread overview]
Message-ID: <48EB7570.3040604@redhat.com> (raw)
In-Reply-To: <48EB302C.1050304@suse.de>
Alexander Graf wrote:
> KVM as is assumes that the kernel obj dir and the kernel source dir are
> at the same location. This is true for most self-built vanilla kernels,
> but some distributions split these up (e.g. SUSE).
> To keep compatible and have users have a good experience on building KVM
> on any distribution, this patch attempts to rebuild the logic from the
> kernel Makefile as closely as possible. With it I successfully built KVM
> on a current SUSE system.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-10-07 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 9:47 [PATCH] [RESEND] Make KVM compile on split source/object kernel configurations Alexander Graf
2008-10-07 14:42 ` 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=48EB7570.3040604@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=alexey.eremenko@qumranet.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).