Re: [RFC workqueue/driver-core PATCH 3/5] driver core: Probe devices asynchronously instead of the driver

2018-09-27 Thread Dan Williams
On Thu, Sep 27, 2018 at 8:31 AM Alexander Duyck wrote: > > > > On 9/26/2018 5:48 PM, Dan Williams wrote: > > On Wed, Sep 26, 2018 at 2:51 PM Alexander Duyck > > wrote: > >> > >> This change makes it so that we probe devices asynchronously instead of the > >> driver. This results in us seeing the

Re: [RFC workqueue/driver-core PATCH 3/5] driver core: Probe devices asynchronously instead of the driver

2018-09-27 Thread Alexander Duyck
On 9/26/2018 5:48 PM, Dan Williams wrote: On Wed, Sep 26, 2018 at 2:51 PM Alexander Duyck wrote: This change makes it so that we 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

Re: [RFC workqueue/driver-core PATCH 3/5] driver core: Probe devices asynchronously instead of the driver

2018-09-26 Thread Dan Williams
On Wed, Sep 26, 2018 at 2:51 PM Alexander Duyck wrote: > > This change makes it so that we 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

[RFC workqueue/driver-core PATCH 3/5] driver core: Probe devices asynchronously instead of the driver

2018-09-26 Thread Alexander Duyck
This change makes it so that we 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