On Tue, 28 Apr 2020, Mark Brown wrote:
On Tue, Apr 28, 2020 at 11:36:38AM +0100, Lee Jones wrote:
On Mon, 27 Apr 2020, Mark Brown wrote:
This completely eliminates the diagnostics which means that if the clock isn't there the user is a bit stuck trying to work out what's missing. There should still be a diagnostic.
The driver won't defer forever though. The final pass should fail with a different error. At which point the error will be released to the system log, no?
One of the really common cases is that someone forgot to build the driver for the dependency so it'll just defer forever waiting for something that never loads.
Need to find another way to identify these failures. There are 10's if not 100's of cases of silently returning if -EPROBE_DEFER is caught.