Re: [PATCH v1] dd: Invoke one probe retry cycle after some initcall levels

2018-09-09 Thread Rafael J. Wysocki
On Mon, Aug 13, 2018 at 7:40 PM Rishabh Bhatnagar wrote: > > From: Rishabh Bhatnagar > > Drivers that are registered at an initcall level may have to > wait until late_init before the probe deferral mechanism can > retry their probe functions. It is possible that their > dependencies were

Re: [PATCH v1] dd: Invoke one probe retry cycle after some initcall levels

2018-09-09 Thread Rafael J. Wysocki
On Mon, Aug 13, 2018 at 7:40 PM Rishabh Bhatnagar wrote: > > From: Rishabh Bhatnagar > > Drivers that are registered at an initcall level may have to > wait until late_init before the probe deferral mechanism can > retry their probe functions. It is possible that their > dependencies were

Re: [PATCH v1] dd: Invoke one probe retry cycle after some initcall levels

2018-09-07 Thread rishabhb
On 2018-08-13 10:39, Rishabh Bhatnagar wrote: From: Rishabh Bhatnagar Drivers that are registered at an initcall level may have to wait until late_init before the probe deferral mechanism can retry their probe functions. It is possible that their dependencies were resolved much earlier, in

Re: [PATCH v1] dd: Invoke one probe retry cycle after some initcall levels

2018-09-07 Thread rishabhb
On 2018-08-13 10:39, Rishabh Bhatnagar wrote: From: Rishabh Bhatnagar Drivers that are registered at an initcall level may have to wait until late_init before the probe deferral mechanism can retry their probe functions. It is possible that their dependencies were resolved much earlier, in

[PATCH v1] dd: Invoke one probe retry cycle after some initcall levels

2018-08-13 Thread Rishabh Bhatnagar
From: Rishabh Bhatnagar Drivers that are registered at an initcall level may have to wait until late_init before the probe deferral mechanism can retry their probe functions. It is possible that their dependencies were resolved much earlier, in some cases even before the next initcall level.

[PATCH v1] dd: Invoke one probe retry cycle after some initcall levels

2018-08-13 Thread Rishabh Bhatnagar
From: Rishabh Bhatnagar Drivers that are registered at an initcall level may have to wait until late_init before the probe deferral mechanism can retry their probe functions. It is possible that their dependencies were resolved much earlier, in some cases even before the next initcall level.

Re: [PATCH v1] dd: Invoke one probe retry cycle after some initcall levels

2018-08-12 Thread Rafael J. Wysocki
On Fri, Aug 10, 2018 at 11:52 PM Rishabh Bhatnagar wrote: > > Drivers that are registered at an initcall level may have to > wait until late_init before the probe deferral mechanism can > retry their probe functions. It is possible that their > dependencies were resolved much earlier, in some

Re: [PATCH v1] dd: Invoke one probe retry cycle after some initcall levels

2018-08-12 Thread Rafael J. Wysocki
On Fri, Aug 10, 2018 at 11:52 PM Rishabh Bhatnagar wrote: > > Drivers that are registered at an initcall level may have to > wait until late_init before the probe deferral mechanism can > retry their probe functions. It is possible that their > dependencies were resolved much earlier, in some

[PATCH v1] dd: Invoke one probe retry cycle after some initcall levels

2018-08-10 Thread Rishabh Bhatnagar
Drivers that are registered at an initcall level may have to wait until late_init before the probe deferral mechanism can retry their probe functions. It is possible that their dependencies were resolved much earlier, in some cases even before the next initcall level. Invoke one probe retry cycle

[PATCH v1] dd: Invoke one probe retry cycle after some initcall levels

2018-08-10 Thread Rishabh Bhatnagar
Drivers that are registered at an initcall level may have to wait until late_init before the probe deferral mechanism can retry their probe functions. It is possible that their dependencies were resolved much earlier, in some cases even before the next initcall level. Invoke one probe retry cycle