On Tue, 15 Jul 2025 22:19:08 +0200, Ahmad Fatoum wrote:
> device_get_match_data returns NULL when no match data is available,
> which a cast to uintptr_t turns into a zero.
>
> Most drivers either put valid pointers into the match data or they
> reserve a literal value of zero to be "unknown".
>
> Three drivers don't do that though and use 0 as valid value for the
> match data and thus the check against zero breaks probing drivers with
> the corresponding match data.
>
> [...]
Applied, thanks!
[1/1] drivers: fix buggy comparisons of casted device_get_match_data to zero
https://git.pengutronix.de/cgit/barebox/commit/?id=964a91e4427f (link may
not be stable)
Best regards,
--
Sascha Hauer <s.ha...@pengutronix.de>
