linux-kernel - Re: [PATCH] KVM: X86: Add mmx movq emulation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FA7A458.3030508@redhat.com>
Date:	Mon, 07 May 2012 13:30:48 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Joerg Roedel <joerg.roedel@....com>
CC:	Marcelo Tosatti <mtosatti@...hat.com>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] KVM: X86: Add mmx movq emulation

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)).

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/