From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: linux rdma 3.14 merge plans Date: Wed, 5 Mar 2014 17:38:17 +0200 Message-ID: <531744E9.4000903@mellanox.com> References: <1389820541.5567.543.camel@haakon3.risingtidesystems.com> <1389906852.5567.668.camel@haakon3.risingtidesystems.com> <1390102949.5567.749.camel@haakon3.risingtidesystems.com> <52DBB4F1.4020400@mellanox.com> <1390375658.5567.917.camel@haakon3.risingtidesystems.com> <1391731323.14985.56.camel@haakon3.risingtidesystems.com> <1394013249.19539.17.camel@haakon3.risingtidesystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Roland Dreier , "Nicholas A. Bellinger" Cc: Hefty Sean , linux-rdma , "Martin K. Petersen" , target-devel , Sagi Grimberg , linux-kernel List-Id: linux-rdma@vger.kernel.org On 05/03/2014 17:18, Roland Dreier wrote: > On Wed, Mar 5, 2014 at 1:54 AM, Nicholas A. Bellinger > wrote: >> >That all said, do you have an objection wrt taking this bits through >> >target-pending..? Given the dependencies involved, that would seem the >> >most logical path to take. > Perhaps not surprisingly, I would prefer to get a chance to review a > major change to the core RDMA midlayer rather than having you merge it > through your tree. So yes I do object. Please give me a chance to > review and merge it. I am working on that this week. Hi Roland, we're very happy to hear that!! As you know, we are soon marking whole five months!! (patches posted Oct 15th/2013) of sitting and waiting to your feedback, lost few upstream releases on the way. Let's get this into the works. Or. Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753905AbaCEPjb (ORCPT ); Wed, 5 Mar 2014 10:39:31 -0500 Received: from eu1sys200aog111.obsmtp.com ([207.126.144.131]:59951 "EHLO eu1sys200aog111.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751967AbaCEPj2 (ORCPT ); Wed, 5 Mar 2014 10:39:28 -0500 Message-ID: <531744E9.4000903@mellanox.com> Date: Wed, 5 Mar 2014 17:38:17 +0200 From: Or Gerlitz User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Roland Dreier , "Nicholas A. Bellinger" CC: Hefty Sean , linux-rdma , "Martin K. Petersen" , target-devel , Sagi Grimberg , linux-kernel Subject: Re: linux rdma 3.14 merge plans References: <1389820541.5567.543.camel@haakon3.risingtidesystems.com> <1389906852.5567.668.camel@haakon3.risingtidesystems.com> <1390102949.5567.749.camel@haakon3.risingtidesystems.com> <52DBB4F1.4020400@mellanox.com> <1390375658.5567.917.camel@haakon3.risingtidesystems.com> <1391731323.14985.56.camel@haakon3.risingtidesystems.com> <1394013249.19539.17.camel@haakon3.risingtidesystems.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.222.66.109] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/03/2014 17:18, Roland Dreier wrote: > On Wed, Mar 5, 2014 at 1:54 AM, Nicholas A. Bellinger > wrote: >> >That all said, do you have an objection wrt taking this bits through >> >target-pending..? Given the dependencies involved, that would seem the >> >most logical path to take. > Perhaps not surprisingly, I would prefer to get a chance to review a > major change to the core RDMA midlayer rather than having you merge it > through your tree. So yes I do object. Please give me a chance to > review and merge it. I am working on that this week. Hi Roland, we're very happy to hear that!! As you know, we are soon marking whole five months!! (patches posted Oct 15th/2013) of sitting and waiting to your feedback, lost few upstream releases on the way. Let's get this into the works. Or. Or.