From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id 73155D075 for ; Fri, 20 Apr 2018 12:49:51 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Apr 2018 03:49:50 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,301,1520924400"; d="scan'208";a="35112577" Received: from irsmsx154.ger.corp.intel.com ([163.33.192.96]) by orsmga008.jf.intel.com with ESMTP; 20 Apr 2018 03:49:49 -0700 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.176]) by IRSMSX154.ger.corp.intel.com ([169.254.12.234]) with mapi id 14.03.0319.002; Fri, 20 Apr 2018 11:48:47 +0100 From: "Mokhtar, Amr" To: "De Lara Guarch, Pablo" , "thomas@monjalon.net" CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev and security Thread-Index: AQHT0v+ZjzkgZXE6FkeAXL4W3wjBfKP/EyFwgAj2kwCAAXo2UA== Date: Fri, 20 Apr 2018 10:48:47 +0000 Message-ID: <3D3765A8CDB52A4C8B410430AA19CB236ECAF5A3@IRSMSX101.ger.corp.intel.com> References: <20180413081439.33050-1-pablo.de.lara.guarch@intel.com> <3D3765A8CDB52A4C8B410430AA19CB236ECA9F09@IRSMSX101.ger.corp.intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjUwOTBiYmYtZjRjYS00NWI2LTgxMmUtZThhNTBlODI2MWYyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJmd3lMSWg4NnhuYXd5eGVjSFJiUEhqdkpUY1wvMkxnRE5KRXpFdDVoNlIybUdSRDFpU3dIN25HM1g1Z0NsVEc1NSJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev and security X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2018 10:49:51 -0000 > -----Original Message----- > From: De Lara Guarch, Pablo > Sent: Thursday 19 April 2018 14:14 > To: Mokhtar, Amr ; thomas@monjalon.net > Cc: dev@dpdk.org > Subject: RE: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev a= nd > security >=20 > Hi Amr, >=20 > > -----Original Message----- > > From: Mokhtar, Amr > > Sent: Friday, April 13, 2018 8:28 PM > > To: De Lara Guarch, Pablo ; > > thomas@monjalon.net > > Cc: dev@dpdk.org > > Subject: RE: [dpdk-dev] [PATCH] maintainers: call out subtree for bbdev > and > > security > > > > Hi Pablo, Thomas, > > There are some update patches undergoing submission for bbdev on > master. > > Do we need to copy them over from master to next-crypto-subtree? > > And how this will work in the future? Will all future patches go to nex= t > subtree > > and back to master? >=20 > Sorry for not replying to this earlier. These patches will get merged in = next- > crypto subtree > and then, after a pull request, Thomas will merge the changes into mainli= ne. >=20 > Pablo Sounds great. Thanks Pablo.