Thread (21 messages) flat view 21 messages, 6 authors, 2018-07-07

Re: [PATCHv3 0/4] drivers/base: bugfix for supplier<-consumer ordering in device_kset

From: Rafael J. Wysocki <hidden>
Date: 2018-07-03 14:36:34
Also in: linux-pci, lkml

On Tuesday, July 3, 2018 8:50:38 AM CEST Pingfan Liu wrote:
commit 52cdbdd49853 ("driver core: correct device's shutdown order")
places an assumption of supplier<-consumer order on the process of probe.
But it turns out to break down the parent <- child order in some scene.
E.g in pci, a bridge is enabled by pci core, and behind it, the devices
have been probed. Then comes the bridge's module, which enables extra
feature(such as hotplug) on this bridge.
So what *exactly* does happen in that case?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help