On Tue, 26 Dec 2017 17:11:19 -0500 (EST)
David Miller wrote:
> From: Stephen Hemminger
> Date: Tue, 26 Dec 2017 13:51:43 -0800
>
> > On Tue, 26 Dec 2017 12:25:12 -0500 (EST)
> > David Miller wrote:
> >
> >> From: Stephen Hemminger
> >> Date: Wed, 20 Dec 2017 14:33:23 -0800
> >>
> >> > S
On Tue, 26 Dec 2017 17:11:19 -0500 (EST)
David Miller wrote:
> From: Stephen Hemminger
> Date: Tue, 26 Dec 2017 13:51:43 -0800
>
> > On Tue, 26 Dec 2017 12:25:12 -0500 (EST)
> > David Miller wrote:
> >
> >> From: Stephen Hemminger
> >> Date: Wed, 20 Dec 2017 14:33:23 -0800
> >>
> >> > S
From: Stephen Hemminger
Date: Tue, 26 Dec 2017 13:51:43 -0800
> On Tue, 26 Dec 2017 12:25:12 -0500 (EST)
> David Miller wrote:
>
>> From: Stephen Hemminger
>> Date: Wed, 20 Dec 2017 14:33:23 -0800
>>
>> > Since commit 6123c66854c1 ("netvsc: delay setup of VF device")
>> > the automatic bring
On Tue, 26 Dec 2017 12:25:12 -0500 (EST)
David Miller wrote:
> From: Stephen Hemminger
> Date: Wed, 20 Dec 2017 14:33:23 -0800
>
> > Since commit 6123c66854c1 ("netvsc: delay setup of VF device")
> > the automatic bring up of the VF is delayed to allow userspace (udev)
> > a chance to rename th
From: Stephen Hemminger
Date: Wed, 20 Dec 2017 14:33:23 -0800
> Since commit 6123c66854c1 ("netvsc: delay setup of VF device")
> the automatic bring up of the VF is delayed to allow userspace (udev)
> a chance to rename the device. This delay is problematic because
> it delays boot and may not be
Since commit 6123c66854c1 ("netvsc: delay setup of VF device")
the automatic bring up of the VF is delayed to allow userspace (udev)
a chance to rename the device. This delay is problematic because
it delays boot and may not be long enough for some cases.
Instead, use the rename can be used to tri
