From: Avi Kivity <avi@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"Christian Bornträger" <christian@borntraeger.net>
Subject: Re: [PATCH linux-next] kvm/powerpc: fix kvm build tree failure
Date: Sun, 28 Jun 2009 10:40:47 +0300 [thread overview]
Message-ID: <4A471E7F.2040907@redhat.com> (raw)
In-Reply-To: <20090626152347.f87cfa4f.sfr@canb.auug.org.au>
On 06/26/2009 08:23 AM, Stephen Rothwell wrote:
> Today's linux-next build (powerpc ppc44x_defconfig) failed like this:
>
> In file included from include/trace/events/kvm.h:57,
> from arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:63:
> include/trace/define_trace.h:53:43: error: trace/events/TRACE_SYSTEM.h: No such file or directory
>
> Caused by commit faa113b7c65c44ed94ac06f6bae2259290040856 ("KVM:
> Protect irq tracing with KVM_HAVE_IOAPIC and KVM_HAVE_PIT").
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-06-28 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 5:23 [PATCH linux-next] kvm/powerpc: fix kvm build tree failure Stephen Rothwell
2009-06-28 7:40 ` 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=4A471E7F.2040907@redhat.com \
--to=avi@redhat.com \
--cc=christian@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.