Re: [PATCH 1/7] Documentation: pm: runtime: Fix a reference to pm_runtime_autosuspend()

[Laurent Pinchart <laurent.pinchart@ideasonboard.com>]

Hi Sakari,

Thank you for the patch.

On Thu, Apr 10, 2025 at 06:31:00PM +0300, Sakari Ailus wrote:
> pm_runtime_autosuspend() got accidentally renamed as
> __pm_runtime_autosuspend() whereas the intention in the patch was to
> rename pm_runtime_put_autosuspend() only. Fix it.
> 
> Fixes: b7d46644e554 ("PM: runtime: Add pm_runtime_put_autosuspend() replacement")
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>

Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> ---
>  Documentation/power/runtime_pm.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/power/runtime_pm.rst b/Documentation/power/runtime_pm.rst
> index 12f429359a82..63344bea8393 100644
> --- a/Documentation/power/runtime_pm.rst
> +++ b/Documentation/power/runtime_pm.rst
> @@ -154,7 +154,7 @@ suspending the device are satisfied) and to queue up a suspend request for the
>  device in that case.  If there is no idle callback, or if the callback returns
>  0, then the PM core will attempt to carry out a runtime suspend of the device,
>  also respecting devices configured for autosuspend.  In essence this means a
> -call to __pm_runtime_autosuspend() (do note that drivers needs to update the
> +call to pm_runtime_autosuspend() (do note that drivers needs to update the
>  device last busy mark, pm_runtime_mark_last_busy(), to control the delay under
>  this circumstance).  To prevent this (for example, if the callback routine has
>  started a delayed suspend), the routine must return a non-zero value.  Negative

-- 
Regards,

Laurent Pinchart