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 to driver probe errors, such regressions can be
addressed much quicker and improve the kernel's stability.
This session will present the approach that is currently being proposed to
detect device probe regressions and open the floor for feedback and discussion.