From: Joerg Roedel <joerg.roedel@amd.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: X86: Add mmx movq emulation
Date: Mon, 7 May 2012 12:44:19 +0200 [thread overview]
Message-ID: <20120507104419.GK4687@amd.com> (raw)
In-Reply-To: <4FA7A458.3030508@redhat.com>
On Mon, May 07, 2012 at 01:30:48PM +0300, Avi Kivity wrote:
> On 05/07/2012 01:28 PM, Joerg Roedel wrote:
> > On Sun, May 06, 2012 at 01:08:05PM +0300, Avi Kivity wrote:
> > > This is already in (cbe2c9d30, e59717550e). Are you looking at master
> > > instead of next?
> >
> > Btw. your mail about the new git-workflow states something about an
> > auto-next branch. But I don't see that branch in the KVM tree (looking
> > at git://git.kernel.org/pub/scm/virt/kvm/kvm.git).
>
> We "forgot" to generate it.
>
> > Is there another
> > branch that contains all fixes and everything for the next merge window?
> > Basically I am looking for a branch which has the new master and next
> > merged.
>
> Right. I'll get my scripts to generate it. (btw: auto-next =
> merge(upstream, master, next)).
Cool thanks. That is perfect for our internal testing :)
Joerg
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
prev parent reply other threads:[~2012-05-07 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 11:47 [PATCH] KVM: X86: Add mmx movq emulation Joerg Roedel
2012-05-06 10:08 ` Avi Kivity
2012-05-07 8:56 ` Joerg Roedel
2012-05-07 9:08 ` Avi Kivity
2012-05-07 10:28 ` Joerg Roedel
2012-05-07 10:30 ` Avi Kivity
2012-05-07 10:44 ` Joerg Roedel [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=20120507104419.GK4687@amd.com \
--to=joerg.roedel@amd.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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