On Mon, 27 Mar 2017 12:21:45 +0100
Ferruh Yigit wrote:
>
> There isn't time left for this release, proposal (v1) deadline is
> passed long ago. Almost integration deadline is hit (end of this
> week).
>
> If your other patches slip into next release, can you please send a
> release notes updates
On 3/27/2017 10:45 AM, Pascal Mazon wrote:
> On Fri, 24 Mar 2017 16:02:48 +
> Ferruh Yigit wrote:
>
>> On 3/22/2017 2:11 PM, Wiles, Keith wrote:
>>>
On Mar 22, 2017, at 3:40 AM, Pascal Mazon
wrote:
Reflect device link status according to the state of the tap
netdevic
On Fri, 24 Mar 2017 16:02:48 +
Ferruh Yigit wrote:
> On 3/22/2017 2:11 PM, Wiles, Keith wrote:
> >
> >> On Mar 22, 2017, at 3:40 AM, Pascal Mazon
> >> wrote:
> >>
> >> Reflect device link status according to the state of the tap
> >> netdevice and the remote netdevice (if any). If both are
On 3/22/2017 2:11 PM, Wiles, Keith wrote:
>
>> On Mar 22, 2017, at 3:40 AM, Pascal Mazon wrote:
>>
>> Reflect device link status according to the state of the tap netdevice
>> and the remote netdevice (if any). If both are UP and RUNNING, then the
>> device link status is set to ETH_LINK_UP, othe
> On Mar 22, 2017, at 3:40 AM, Pascal Mazon wrote:
>
> Reflect device link status according to the state of the tap netdevice
> and the remote netdevice (if any). If both are UP and RUNNING, then the
> device link status is set to ETH_LINK_UP, otherwise ETH_LINK_DOWN.
>
> Signed-off-by: Pascal
Reflect device link status according to the state of the tap netdevice
and the remote netdevice (if any). If both are UP and RUNNING, then the
device link status is set to ETH_LINK_UP, otherwise ETH_LINK_DOWN.
Signed-off-by: Pascal Mazon
---
drivers/net/tap/rte_eth_tap.c | 32 +++
6 matches
Mail list logo
