From: Avi Kivity <avi@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 7 (kvm)
Date: Thu, 08 Mar 2012 13:53:59 +0200 [thread overview]
Message-ID: <4F589DD7.1040704@redhat.com> (raw)
In-Reply-To: <4F57E791.6070205@xenotime.net>
On 03/08/2012 12:56 AM, Randy Dunlap wrote:
> On 03/06/2012 11:10 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20120306:
> >
> > The kvm tree lost its build failure.
>
>
> I'm getting this build error on X86_32 (i386):
>
> arch/x86/kvm/x86.c:1042: Error: no instruction mnemonic suffix given and no register operands; can't size instruction
>
>
Patch to follow.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-03-08 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 7:10 linux-next: Tree for Mar 7 Stephen Rothwell
2012-03-07 22:56 ` linux-next: Tree for Mar 7 (kvm) Randy Dunlap
2012-03-08 11:53 ` 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=4F589DD7.1040704@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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).