From mboxrd@z Thu Jan 1 00:00:00 1970 From: Catalin Marinas Subject: Re: [PATCH v2 5/5] arm64/xen: introduce CONFIG_XEN and hypercall.S on ARM64 Date: Wed, 5 Jun 2013 14:21:17 +0100 Message-ID: <20130605132117.GK8758@arm.com> References: <1370273624-26976-5-git-send-email-stefano.stabellini@eu.citrix.com> <20130603162517.GC32295@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Stefano Stabellini Cc: "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "xen-devel@lists.xensource.com" , Will Deacon , "Ian.Campbell@citrix.com" , "konrad.wilk@oracle.com" List-Id: xen-devel@lists.xenproject.org On Mon, Jun 03, 2013 at 05:51:53PM +0100, Stefano Stabellini wrote: > On Mon, 3 Jun 2013, Catalin Marinas wrote: > > Otherwise, the series looks good. How do you plan to upstream this? > > Good question. > Traditionally Xen stuff goes to Linus directly via one of the Xen trees > (Konrad's or mine), but since this is the very first Xen patch series > for arm64 if you prefer I can submit a pull request to you instead. > Just let me know, I am happy either way. I can take the first series and subsequent merges can go via the Xen tree (KVM has a similar approach). > In any case, are you OK with sending it upstream during the next merge > window? Yes, if I get a pull request in time ;) -- Catalin