Regressions that cause a device to no longer be probed by a driver can have a
big impact on the platform's functionality, and despite being relatively common
there isn't currently any generic way to detect them.
By enabling the community to catch device probe regressions in a way that
doesn't require additional work for every new platform, and that can catch
issues from config changes...
The current CI systems for the kernel offer basic and low-level
regression detection and handling capabilities based on test results, but they do that in their own specific way. We wonder if we can find more common ways of tackling the problem through post-processing the data provided by the different CI systems. We could then extract additional "hidden" information, look at failure trends,...