Re: [PATCH 2/2] driver core: power: Fix "sucessfully" typo in comment

On Mon, Aug 24, 2026 at 12:01:21PM +0545, Chhabilal Dangal wrote:
> Signed-off-by: Chhabilal Dangal <[email protected]>
> ---
>  drivers/base/power/clock_ops.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/base/power/clock_ops.c b/drivers/base/power/clock_ops.c
> index 59bb37e82..3b8ba2780 100644
> --- a/drivers/base/power/clock_ops.c
> +++ b/drivers/base/power/clock_ops.c
> @@ -250,7 +250,7 @@ EXPORT_SYMBOL_GPL(pm_clk_add);
>   *
>   * Add the clock to the list of clocks used for the power management of @dev.
>   * The power-management code will take control of the clock reference, so
> - * callers should not call clk_put() on @clk after this function sucessfully
> + * callers should not call clk_put() on @clk after this function successfully
>   * returned.
>   */
>  int pm_clk_add_clk(struct device *dev, struct clk *clk)
> -- 
> 2.55.0
> 

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 did not specify a description of why the patch is needed, or
  possibly, any description at all, in the email body.  Please read the
  section entitled "The canonical patch format" in the kernel file,
  Documentation/process/submitting-patches.rst for what is needed in
  order to properly describe the change.

- This looks like a new version of a previously submitted patch, but you
  did not list below the --- line any changes from the previous version.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for what
  needs to be done here to properly describe 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