From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54730) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WAmYH-0005zN-1V for qemu-devel@nongnu.org; Tue, 04 Feb 2014 15:25:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WAmYB-0001tB-6n for qemu-devel@nongnu.org; Tue, 04 Feb 2014 15:25:00 -0500 Received: from mail-pa0-f44.google.com ([209.85.220.44]:44796) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WAmYB-0001t3-1M for qemu-devel@nongnu.org; Tue, 04 Feb 2014 15:24:55 -0500 Received: by mail-pa0-f44.google.com with SMTP id kq14so8954286pab.31 for ; Tue, 04 Feb 2014 12:24:54 -0800 (PST) Date: Tue, 4 Feb 2014 12:25:00 -0800 From: Christoffer Dall Message-ID: <20140204202500.GP4167@cbox> References: <1391383044-596-1-git-send-email-christoffer.dall@linaro.org> <20140203005539.GC2469@cbox> <20140204200738.GO4167@cbox> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v6 0/6] Support arm-gic-kvm save/restore List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Patch Tracking , QEMU Developers , "kvmarm@lists.cs.columbia.edu" On Tue, Feb 04, 2014 at 08:09:52PM +0000, Peter Maydell wrote: > On 4 February 2014 20:07, Christoffer Dall wrote: > > On Tue, Feb 04, 2014 at 07:56:27PM +0000, Peter Maydell wrote: > >> Thanks; I've applied 1-5 to target-arm.next. > >> (Incidentally you could make my job a little easier by keeping > >> the 'changes between v3 and v4' commentary after the '---' line > >> so I don't have to edit it out of the commit messages.) > >> > > You mean on the git commits? I've done that on the patches themselves > > if you pick them off the list. Should probably do that for the git > > commits as well (or just leave them off there completely). > > Yeah, I pulled these off your git branch; usually I'd go by > the patches on the list, but Anthony's patches database isn't > updating at the moment, so using the git branch was easier. > ok, I'll push a more apply-able git branch in the future. -Christoffer