Hi Greg at al, These fix two issues on top of the recent device links material in driver-core/driver-core-next.
The first one fixes a race condition that may trigger when __pm_runtime_set_status() is used incorrectly (that is, when it is called with PM-runtime enabled for the target device and working). The second one fixes a supplier PM-runtime usage counter imbalance resulting from adding and removing (e.g. in the error code path) a stateless device link to it from within the consumer driver's probe callback. Please refer to the patch changelogs for details. Cheers, Rafael
