From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 5A88DB38C for ; Tue, 16 Sep 2014 16:21:18 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 16 Sep 2014 07:26:53 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,534,1406617200"; d="scan'208";a="600389148" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by fmsmga002.fm.intel.com with ESMTP; 16 Sep 2014 07:26:20 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.112]) by IRSMSX102.ger.corp.intel.com ([169.254.2.24]) with mapi id 14.03.0195.001; Tue, 16 Sep 2014 15:26:07 +0100 From: "Richardson, Bruce" To: Thomas Monjalon Thread-Topic: Patch merges for 1.8 release Thread-Index: Ac/Rl5TQ4hX/VVhxR/qzBkj1dsDEAgAGWJ2AAAJGJVA= Date: Tue, 16 Sep 2014 14:26:07 +0000 Message-ID: <59AF69C657FD0841A61C55336867B5B0343F27B0@IRSMSX103.ger.corp.intel.com> References: <20140916101838.GA1484@BRICHA3-MOBL> <2048283.MNpMd1jf3I@xps13> In-Reply-To: <2048283.MNpMd1jf3I@xps13> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Patch merges for 1.8 release X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 14:21:18 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Tuesday, September 16, 2014 3:20 PM > To: Richardson, Bruce > Cc: dev@dpdk.org > Subject: Re: Patch merges for 1.8 release >=20 > Hi Bruce, >=20 > 2014-09-16 11:18, Bruce Richardson: > > I'm just wondering what the expected timeline is for you starting to me= rge > patches in for the 1.8 release? As you have > > probably seen, I have quite a number of outstanding patches submitted f= or > mbufs, and I'm wonder when the "part 1" set, > > which by now has been pretty well reviewed and ack'ed, might be merged = to > the mainline? I'm loath to start upstreaming > > drafts of part 3 patches at this stage, because the depth of the backlo= g I'm > building up just increases the amount > > of work I have to do for any mainline changes that require me to do cha= nges > on rebase. >=20 > I was very busy last week with DPDK summit and IDF. > Now I'm back and I'm cleaning up the patchwork tool (before availability > announcement in a couple of days). > Then the goal of the next days is to make a -rc1 tag with all the patches > which are ready and properly reviewed. > The mbuf changes are first in my list. >=20 Thanks for the info, and welcome back! /Bruce