On Wed, May 18, 2016 at 05:18:41PM +0200, Alexander Stein wrote: > Well, it's debatable if using dev_err() and then returning EPROBE_DEFER is > correct either. IMHO if there is an actual error, an error code has to be > returned and not "well, can't continue now, probe me again later". > At first glance those EPROBE_DEFER are correct as other dependent drivers may > be probed later, so printing an error in that case seems wrong to me. Half the point with probe deferral is that it's transparent to anything that isn't actually resolving a resource - if we have to add custom code in to everywhere were we need to print an error in a probe path that's not great either. We also don't want to silently ignore probe deferral all the time since then it becomes very hard to diagnose why something is not instantiating.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
