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 Apr 24 (kvm)
Date: Wed, 25 Apr 2012 12:35:01 +0300 [thread overview]
Message-ID: <4F97C545.4030304@redhat.com> (raw)
In-Reply-To: <4F96D3FA.1010909@xenotime.net>
On 04/24/2012 07:25 PM, Randy Dunlap wrote:
> On 04/23/2012 10:43 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > There will probably be no linux-next release until April 30 as I am
> > taking a break.
> >
> > Changes since 20120423:
>
>
> on i386:
>
> CC [M] arch/x86/kvm/emulate.o
> arch/x86/kvm/emulate.c: Assembler messages:
> arch/x86/kvm/emulate.c:4122: Error: bad register name `%bpl'
>
>
Fix already committed, will be pushed later today.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2012-04-25 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 5:43 linux-next: Tree for Apr 24 Stephen Rothwell
2012-04-24 16:25 ` linux-next: Tree for Apr 24 (kvm) Randy Dunlap
2012-04-25 9:35 ` 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=4F97C545.4030304@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).