From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: Vendor specific sub-trees under next-net
Date: Fri, 13 Oct 2017 01:51:25 +0200
Message-ID: <9041864.FpAEQS7Gje@xps>
References: <a6c5a18e-5898-2120-a7fb-7e28f1ae0e99@intel.com>
 <15fd757d-d540-d787-f525-2c881502970a@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: DPDK <dev@dpdk.org>, "Zhang, Helin" <helin.zhang@intel.com>,
 Olga Shern <olgas@mellanox.com>, Jerin Jacob <jerin.jacob@caviumnetworks.com>,
 Hemant Agrawal <hemant.agrawal@nxp.com>, Gaetan Rivet <gaetan.rivet@6wind.com>,
 Pascal Mazon <pascal.mazon@6wind.com>, "Zhu, Heqing" <heqing.zhu@intel.com>,
 John McNamara <john.mcnamara@intel.com>,
 Vincent JARDIN <vincent.jardin@6wind.com>, shahafs@mellanox.com
To: Ferruh Yigit <ferruh.yigit@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
 [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 639711B390
 for <dev@dpdk.org>; Fri, 13 Oct 2017 01:51:27 +0200 (CEST)
In-Reply-To: <15fd757d-d540-d787-f525-2c881502970a@intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

13/10/2017 01:31, Ferruh Yigit:
> 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.

Good news, thanks

> 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?

Yes every dpdk.org git trees must be approved by the techboard.
The next meeting is tomorrow.

> 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.

Yes we are creating a new git tree layer below next-net.

> This will distribute the maintenance work among the vendors, also will
> give more control to vendors on their patches.

It is very good to distribute workload.
In 17.11-rc1, there were more than 500 patches managed in next-net.
Thanks Ferruh

> Thanks,
> ferruh
> 
> 
> [1]
> http://dpdk.org/ml/archives/dev/2017-September/075094.html
> 
> [2]
> http://dpdk.org/ml/archives/dev/2017-October/078277.html