From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51332) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VOWYx-0008Co-4J for qemu-devel@nongnu.org; Tue, 24 Sep 2013 13:38:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VOWYs-0005FD-LP for qemu-devel@nongnu.org; Tue, 24 Sep 2013 13:38:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37466) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VOWYs-0005F9-Dg for qemu-devel@nongnu.org; Tue, 24 Sep 2013 13:38:10 -0400 From: Juan Quintela In-Reply-To: <5241CA14.3010300@linux.vnet.ibm.com> (Michael R. Hines's message of "Tue, 24 Sep 2013 13:21:24 -0400") References: <5d53d839653bf4fd24d5cb56f6d24d3dc3f8f8a5.1378261891.git.yamahata@private.email.ne.jp> <5239B8A3.10305@linux.vnet.ibm.com> <20130920075546.GP16551@valinux.co.jp> <523C5779.4010309@linux.vnet.ibm.com> <87wqm6p462.fsf@elfo.elfo> <5241CA14.3010300@linux.vnet.ibm.com> Date: Tue, 24 Sep 2013 19:38:03 +0200 Message-ID: <87siwup1c4.fsf@elfo.elfo> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [PATCH 1/2] rdma: constify ram_chunk_{index, start, end} Reply-To: quintela@redhat.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael R. Hines" Cc: Isaku Yamahata , owasserm@redhat.com, pbonzini@redhat.com, mrhines@us.ibm.com, qemu-devel@nongnu.org "Michael R. Hines" wrote: > On 09/24/2013 12:36 PM, Juan Quintela wrote: >> "Michael R. Hines" wrote: >>> On 09/20/2013 03:55 AM, Isaku Yamahata wrote: >>>> On Wed, Sep 18, 2013 at 10:28:51AM -0400, Michael R. Hines wrote: >>>>> On 09/03/2013 10:32 PM, Isaku Yamahata wrote: >>>>>> Signed-off-by: Isaku Yamahata >>> There's no need to rebase against github or track my branches. >>> >>> Just use qemu.org master. >> Michael, I sent this on my pull request (it was trivial enough). >> How do you want to track migration-rdma patches? Should they pass >> through you, or should I pick them depending on your Ack/Nack? >> >> Later, Juan. >> > > That's a good question - as I'm also new to the maintenance process, > what would you recommend? > > I will definitely be contributing/monitoring/reviewing the RDMA code > for the forseeable future.... I integrate it, and in migration-rdma.c, I wait for your nack/ack. what do you think? Later, Juan.