From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 730B01B351 for ; Fri, 13 Oct 2017 01:31:20 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Oct 2017 16:31:19 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.43,368,1503385200"; d="scan'208";a="909447787" Received: from unknown (HELO [10.241.225.21]) ([10.241.225.21]) by FMSMGA003.fm.intel.com with ESMTP; 12 Oct 2017 16:31:18 -0700 From: Ferruh Yigit To: DPDK , "Zhang, Helin" , Thomas Monjalon , Olga Shern , Jerin Jacob , Hemant Agrawal , Gaetan Rivet , Pascal Mazon Cc: "Zhu, Heqing" , John McNamara , Vincent JARDIN References: Message-ID: <15fd757d-d540-d787-f525-2c881502970a@intel.com> Date: Fri, 13 Oct 2017 00:31:18 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] Vendor specific sub-trees under next-net 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: Thu, 12 Oct 2017 23:31:20 -0000 On 10/13/2017 12:29 AM, Ferruh Yigit wrote: > Hi Thomas, et al > > Previously it has been mentioned [1] to have vendor specific driver > trees under next-net. > > And recently Mellanox agreed to have a Mellanox tree [2]. > > Intel also agrees to have next-net-intel, and Helin will be maintaining > it, thanks to Helin for volunteering. > > Other vendors with multiple drivers are Cavium, 6wind and NXP. > > > - Is there a name for Mellanox maintainer? > > - What do other vendors, mentioned above, thinks about creating their > own sub-tree? > > - Are the vendor sub-trees and their maintainers need to be approved by > tech-board? > > > And what I understand from vendor specific sub-trees is, instead of > driver patches going into next-net directly, they will go into vendor > tree and next-net will pull from them. > > This will distribute the maintenance work among the vendors, also will > give more control to vendors on their patches. > > > Thanks, > ferruh > > > [1] > http://dpdk.org/ml/archives/dev/2017-September/075094.html > > [2] > http://dpdk.org/ml/archives/dev/2017-October/078277.html > Using correct mail address for Thomas.