Re: [dpdk-dev] Vendor specific sub-trees under next-net

[Ferruh Yigit <ferruh.yigit@intel.com>]

On 10/15/2017 6:28 AM, Shahaf Shuler wrote:
> Friday, October 13, 2017 2:31 AM, Ferruh Yigit:
>> 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?
> 
> I will be the maintainer of Mellanox tree. 
> 
>>>
>>> - 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.
> 
> We need to define this more carefully.
> Sometimes a patchset has driver patches but also some patches for ethdev and testpmd/example.
> 
> What if other vendor would like to use those patches?
> How frequent will be the merging between the vendor-specific tree and next-net?

I am for a more frequent merge, like a weekly one, we can define a
branch for merge, what ever you put into there can be merged weekly.

Frequent merge is good for sync, as you mentioned, also good for giving
time to vendor sub-trees for change if change requested before merging
into next-net, as Hemant mentioned.

And we can discuss and change it according if it is working fine or not.

Thanks,
ferruh

> 
> Am not saying there is an issue here, just need to define the rules. 
> 
>>>
>>> This will distribute the maintenance work among the vendors, also will
>>> give more control to vendors on their patches.
>>>
>>>
>>> Thanks,
>>> ferruh
>>>
>>>
>>> [1]
>>>
>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpd
>> k
>>> .org%2Fml%2Farchives%2Fdev%2F2017-
>> September%2F075094.html&data=02%7C01
>>>
>> %7Cshahafs%40mellanox.com%7Cb9cdfab0a0544608bd4708d511c9597f%7Ca
>> 652971
>>>
>> c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636434478859873082&sdata=A15
>> iL0two
>>> 9nLROmTBRUf54xCZxn%2BwLCAuZNLLyNnTqE%3D&reserved=0
>>>
>>> [2]
>>>
>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpd
>> k
>>> .org%2Fml%2Farchives%2Fdev%2F2017-
>> October%2F078277.html&data=02%7C01%7
>>>
>> Cshahafs%40mellanox.com%7Cb9cdfab0a0544608bd4708d511c9597f%7Ca652
>> 971c7
>>>
>> d2e4d9ba6a4d149256f461b%7C0%7C0%7C636434478859873082&sdata=%2B9
>> tWsEXRf
>>> PDZJfPqYrcRCuYmRCB3Ix7I%2FzjGwHZNbSI%3D&reserved=0
>>>
>>
>> Using correct mail address for Thomas.