Hello,Hi Uwe,
On Mon, Jun 17, 2024 at 04:44:13PM +0800, Junyi Zhao wrote:
Please keep the dev_err_probe(). There is a problem with that approachHi Uwe, I didnt get the clear point.So yes, please use dev_err_probe() also to handleMy point here is also that devm_add_action_or_reset() can only fail on
devm_add_action_or_reset().
memory allocation, like (devm_)kzalloc. Looking around the kernel, we
tend to not add messages for that and just return the error code,
presumably because those same 'out of memory' messages would proliferate
everywhere.
So, if we need "return ret" directly? or keep "dev_err_probe()" to print?
(as Jerome pointed out), but that is about to be addressed in driver
core code.
Best regards
Uwe