[dpdk-dev] Vendor specific sub-trees under next-net
ferruh.yigit at intel.com
Fri Oct 13 01:29:43 CEST 2017
Hi Thomas, et al
Previously it has been mentioned  to have vendor specific driver
trees under next-net.
And recently Mellanox agreed to have a Mellanox tree .
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
- Are the vendor sub-trees and their maintainers need to be approved by
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.
More information about the dev