Michael S. Tsirkin wrote:
>On Thu, Mar 22, 2018 at 12:02:10PM +, Jay Vosburgh wrote:
>> Michael S. Tsirkin wrote:
>>
>> >On Thu, Mar 22, 2018 at 09:05:52AM +, Jay Vosburgh wrote:
>> >> The operstate update logic will leave an interface in the
>> >> default UNKNOWN operstate if the int
On Thu, Mar 22, 2018 at 12:02:10PM +, Jay Vosburgh wrote:
> Michael S. Tsirkin wrote:
>
> >On Thu, Mar 22, 2018 at 09:05:52AM +, Jay Vosburgh wrote:
> >>The operstate update logic will leave an interface in the
> >> default UNKNOWN operstate if the interface carrier state never change
Michael S. Tsirkin wrote:
>On Thu, Mar 22, 2018 at 09:05:52AM +, Jay Vosburgh wrote:
>> The operstate update logic will leave an interface in the
>> default UNKNOWN operstate if the interface carrier state never changes
>> from the default carrier up state set at creation. This includes
On Thu, Mar 22, 2018 at 09:05:52AM +, Jay Vosburgh wrote:
> The operstate update logic will leave an interface in the
> default UNKNOWN operstate if the interface carrier state never changes
> from the default carrier up state set at creation. This includes the
> case of an explicit call
The operstate update logic will leave an interface in the
default UNKNOWN operstate if the interface carrier state never changes
from the default carrier up state set at creation. This includes the
case of an explicit call to netif_carrier_on, as the carrier on to on
transition has no effe
