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 agree
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 al
Hi Ferruh,
On 10/13/2017 5:21 AM, Thomas Monjalon wrote:
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-int
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, thank
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
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 m
6 matches
Mail list logo
