From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ferruh.yigit@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id 3E77D1B351
 for <dev@dpdk.org>; Fri, 13 Oct 2017 01:29:45 +0200 (CEST)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
 by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
 12 Oct 2017 16:29:44 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.43,368,1503385200"; d="scan'208";a="909447264"
Received: from unknown (HELO [10.241.225.21]) ([10.241.225.21])
 by FMSMGA003.fm.intel.com with ESMTP; 12 Oct 2017 16:29:43 -0700
To: DPDK <dev@dpdk.org>, "Zhang, Helin" <helin.zhang@intel.com>,
 Thomas Monjalon <thomas.monjalon@6wind.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>
From: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "Zhu, Heqing" <heqing.zhu@intel.com>,
 John McNamara <john.mcnamara@intel.com>,
 Vincent JARDIN <vincent.jardin@6wind.com>
Message-ID: <a6c5a18e-5898-2120-a7fb-7e28f1ae0e99@intel.com>
Date: Fri, 13 Oct 2017 00:29:43 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: [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 <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>
X-List-Received-Date: Thu, 12 Oct 2017 23:29:46 -0000

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