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
Subject: Re: linux-next: kvm tree build failure
Date: Thu, 13 Aug 2009 11:58:20 +0300 [thread overview]
Message-ID: <4A83D5AC.1030503@redhat.com> (raw)
In-Reply-To: <20090813125840.048af293.sfr@canb.auug.org.au>
On 08/13/2009 05:58 AM, Stephen Rothwell wrote:
> Hi Avi,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> x86_64-linux-gcc: arch/x86/kvm/x86_emulate.c: No such file or directory
>
> Caused by commit 5383e9982ee230b06b3c385e675ae6fc7846c40f ("KVM: Rename
> x86_emulate.c to emulate.c").
>
> I have used the version of the kvm tree from next-20090812 for today.
>
Fixed now, don't know how such brokenness slipped out.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-13 8:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 2:58 linux-next: kvm tree build failure Stephen Rothwell
2009-08-13 8:58 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-19 1:42 Stephen Rothwell
2010-01-19 7:57 ` Avi Kivity
2010-01-19 9:42 ` Stephen Rothwell
2010-01-11 8:07 Stephen Rothwell
2010-01-11 8:21 ` Stephen Rothwell
2010-01-11 10:27 ` Avi Kivity
2009-06-23 5:53 Stephen Rothwell
2009-06-23 10:23 ` Avi Kivity
2009-06-18 1:11 Stephen Rothwell
2009-06-18 4:25 ` Jaswinder Singh Rajput
2009-06-18 9:49 ` Avi Kivity
2009-05-21 7:21 Stephen Rothwell
2009-05-21 7:32 ` Avi Kivity
2009-05-21 7:37 ` Boaz Harrosh
2009-05-21 7:39 ` Avi Kivity
2009-05-21 7:48 ` Boaz Harrosh
2009-05-21 10:05 ` Avi Kivity
2008-12-22 13:25 Stephen Rothwell
2008-12-29 5:17 ` Stephen Rothwell
2009-01-02 0:53 ` Stephen Rothwell
2009-01-04 11:08 ` Avi Kivity
2009-01-04 19:45 ` Hollis Blanchard
2009-01-04 19:55 ` Avi Kivity
2008-12-18 11:05 Stephen Rothwell
2008-10-15 5:47 Stephen Rothwell
2008-10-15 13:25 ` Avi Kivity
2008-09-17 7:01 Stephen Rothwell
2008-09-17 8:50 ` Ingo Molnar
2008-09-24 12:39 ` Avi Kivity
2008-09-24 16:18 ` Jesse Barnes
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=4A83D5AC.1030503@redhat.com \
--to=avi@redhat.com \
--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 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).