Re: [driver-core PATCH v6 6/9] driver core: Probe devices asynchronously instead of the driver

2018-11-27 Thread Dan Williams
On Tue, Nov 27, 2018 at 9:58 AM Alexander Duyck wrote: > > On Mon, 2018-11-26 at 18:48 -0800, Dan Williams wrote: > > On Thu, Nov 8, 2018 at 10:07 AM Alexander Duyck > > wrote: > > > > > > Probe devices asynchronously instead of the driver. This results in us > > > seeing the same behavior if

Re: [driver-core PATCH v6 6/9] driver core: Probe devices asynchronously instead of the driver

2018-11-27 Thread Alexander Duyck
On Mon, 2018-11-26 at 18:48 -0800, Dan Williams wrote: > On Thu, Nov 8, 2018 at 10:07 AM Alexander Duyck > wrote: > > > > Probe devices asynchronously instead of the driver. This results in us > > seeing the same behavior if the device is registered before the driver or > > after. This way we

Re: [driver-core PATCH v6 6/9] driver core: Probe devices asynchronously instead of the driver

2018-11-26 Thread Dan Williams
On Thu, Nov 8, 2018 at 10:07 AM Alexander Duyck wrote: > > Probe devices asynchronously instead of the driver. This results in us > seeing the same behavior if the device is registered before the driver or > after. This way we can avoid serializing the initialization should the > driver not be

Re: [driver-core PATCH v6 6/9] driver core: Probe devices asynchronously instead of the driver

2018-11-08 Thread Bart Van Assche
On Thu, 2018-11-08 at 10:07 -0800, Alexander Duyck wrote: > Probe devices asynchronously instead of the driver. This results in us > seeing the same behavior if the device is registered before the driver or > after. This way we can avoid serializing the initialization should the > driver not be

[driver-core PATCH v6 6/9] driver core: Probe devices asynchronously instead of the driver

2018-11-08 Thread Alexander Duyck
Probe devices asynchronously instead of the driver. This results in us seeing the same behavior if the device is registered before the driver or after. This way we can avoid serializing the initialization should the driver not be loaded until after the devices have already been added. The