On Thu, Jul 04, 2024 at 10:52:08AM +0200, Neil Armstrong wrote: > If the thermal core tries to update the temperature from an > uninitialized power supply, it will swawn the following warning: > thermal thermal_zoneXX: failed to read out thermal zone (-19) > > But reading from an uninitialized power supply should not be > considered as a fatal error, but the thermal core expects > the -EAGAIN error to be returned in this particular case. > > So convert -ENODEV as -EAGAIN to express the fact that reading > temperature from an uninitialized power supply shouldn't be > a fatal error, but should indicate to the thermal zone it should > retry later. > > It notably removes such messages on Qualcomm platforms using the > qcom_battmgr driver spawning warnings until the aDSP firmware > gets up and the battery manager reports valid data. > > Link: https://lore.kernel.org/all/2ed4c630-204a-4f80-a37f-f2ca838eb455@xxxxxxxxxx/ > Fixes: 5bc28b93a36e ("power_supply: power_supply_read_temp only if use_cnt > 0") > Fixes: 3be330bf8860 ("power_supply: Register battery as a thermal zone") > Signed-off-by: Neil Armstrong <neil.armstrong@xxxxxxxxxx> > --- > drivers/power/supply/power_supply_core.c | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - You have marked a patch with a "Fixes:" tag for a commit that is in an older released kernel, yet you do not have a cc: stable line in the signed-off-by area at all, which means that the patch will not be applied to any older kernel releases. To properly fix this, please follow the documented rules in the Documentation/process/stable-kernel-rules.rst file for how to resolve this. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot
