From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Zyngier Subject: Re: [kvmarm] [GIT PULL v2] KVM/ARM Fixes for 3.9-rc1 Date: Thu, 07 Mar 2013 07:57:23 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Marcelo Tosatti , Gleb Natapov , KVM General , To: Christoffer Dall Return-path: Received: from inca-roads.misterjones.org ([213.251.177.50]:59119 "EHLO inca-roads.misterjones.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751039Ab3CGG52 (ORCPT ); Thu, 7 Mar 2013 01:57:28 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Wed, 6 Mar 2013 20:40:00 -0800, Christoffer Dall wrote: > On Wed, Mar 6, 2013 at 7:54 PM, Marc Zyngier wrote: >> On Wed, 6 Mar 2013 16:31:48 -0800, Christoffer Dall >> >> wrote: >> >> Hi Christoffer, >> >>> >>> Please pull these KVM/ARM fixes mostly centered around preparation for >>> Marc's ARMv8 KVM work. >> >> Can we please hold on that for a while? asm-offset.c is usually a >> candidate for merge conflicts as people start pushing patches post merge >> window, and it would make sense to see what is happening in that space. >> > Sure, when would you see this happen exactly? Usually, by -rc5 we have a pretty good idea of what is going in. Also, putting things into -next is a good way to detect potential problems. Oh, and keeping linux-arm-kernel into the loop. Most ARM developers don't follow the KVM lists. M. -- Fast, cheap, reliable. Pick two.