Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 4d88a97aa9e8 libnvdimm, nvdimm: dimm driver and base libnvdimm
device-driver infrastructure.
The bot has tested the following trees: v5.2.1, v5.1.18, v4.19.59, v4.14.133,
v4.9.185, v4.4.185.
v5.2.1: Build OK!
v5.1.18: Build OK!
v4.19.59: Failed to apply! Possible dependencies:
3451a495ef24 ("driver core: Establish order of operations for device_add
and device_del via bitflag")
v4.14.133: Failed to apply! Possible dependencies:
3451a495ef24 ("driver core: Establish order of operations for device_add
and device_del via bitflag")
v4.9.185: Failed to apply! Possible dependencies:
3451a495ef24 ("driver core: Establish order of operations for device_add
and device_del via bitflag")
v4.4.185: Failed to apply! Possible dependencies:
3451a495ef24 ("driver core: Establish order of operations for device_add
and device_del via bitflag")
656b8035b0ee ("ARM: 8524/1: driver cohandle -EPROBE_DEFER from
bus_type.match()")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
_______________________________________________
Linux-nvdimm mailing list
[email protected]
https://lists.01.org/mailman/listinfo/linux-nvdimm
