linux-kernel - Re: [PATCH] PM: runtime: fix typos in runtime.c comments

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJZ5v0gtKTUAthA4OaCU-hV4j1OhRDuA10o-ZhXepFyq7J5L2g@mail.gmail.com>
Date: Wed, 29 Oct 2025 20:00:20 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Malaya Kumar Rout <mrout@...hat.com>
Cc: linux-kernel@...r.kernel.org, lyude@...hat.com, malayarout91@...il.com, 
	"Rafael J. Wysocki" <rafael@...nel.org>, Pavel Machek <pavel@...nel.org>, Len Brown <lenb@...nel.org>, 
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Danilo Krummrich <dakr@...nel.org>, linux-pm@...r.kernel.org
Subject: Re: [PATCH] PM: runtime: fix typos in runtime.c comments

On Sun, Oct 26, 2025 at 6:05 PM Malaya Kumar Rout <mrout@...hat.com> wrote:
>
> Fix several typos in comments:
> - "timesptamp" -> "timestamp"
> - "involed" -> "involved"
> - "nonero" -> "nonzero"
>
> Fix typos in comments to improve code documentation clarity.
>
> Signed-off-by: Malaya Kumar Rout <mrout@...hat.com>
> ---
>  drivers/base/power/runtime.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/base/power/runtime.c b/drivers/base/power/runtime.c
> index 1b11a3cd4acc..7fe63cab2708 100644
> --- a/drivers/base/power/runtime.c
> +++ b/drivers/base/power/runtime.c
> @@ -90,7 +90,7 @@ static void update_pm_runtime_accounting(struct device *dev)
>         /*
>          * Because ktime_get_mono_fast_ns() is not monotonic during
>          * timekeeping updates, ensure that 'now' is after the last saved
> -        * timesptamp.
> +        * timestamp.
>          */
>         if (now < last)
>                 return;
> @@ -217,7 +217,7 @@ static int dev_memalloc_noio(struct device *dev, void *data)
>   *     resume/suspend callback of any one of its ancestors(or the
>   *     block device itself), the deadlock may be triggered inside the
>   *     memory allocation since it might not complete until the block
> - *     device becomes active and the involed page I/O finishes. The
> + *     device becomes active and the involved page I/O finishes. The
>   *     situation is pointed out first by Alan Stern. Network device
>   *     are involved in iSCSI kind of situation.
>   *
> @@ -1210,7 +1210,7 @@ EXPORT_SYMBOL_GPL(__pm_runtime_resume);
>   *
>   * Otherwise, if its runtime PM status is %RPM_ACTIVE and (1) @ign_usage_count
>   * is set, or (2) @dev is not ignoring children and its active child count is
> - * nonero, or (3) the runtime PM usage counter of @dev is not zero, increment
> + * nonzero, or (3) the runtime PM usage counter of @dev is not zero, increment
>   * the usage counter of @dev and return 1.
>   *
>   * Otherwise, return 0 without changing the usage counter.
> --

Applied as 6.19 material, thanks!