linux-kernel - Re: [PATCH] timer: Fix some typos in timer module

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAHP3+4AHs-Uo=9eOgCv_hNb6HmZ3n4zvces6Yz5AC5YciH55Xg@mail.gmail.com>
Date: Thu, 9 Oct 2025 10:55:30 +0800
From: Jianyun Gao <jianyungao89@...il.com>
To: linux-kernel@...r.kernel.org
Cc: Anna-Maria Behnsen <anna-maria@...utronix.de>, Frederic Weisbecker <frederic@...nel.org>, 
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] timer: Fix some typos in timer module

Could someone please review this patch for me? Thank you very much.

On Sat, Sep 27, 2025 at 5:34 PM Jianyun Gao <jianyungao89@...il.com> wrote:
>
> There are some typos in timer module, as below:
>
>   presicion ==> precision
>   gobal ==> global
>   exectued ==> executed
>   refere ==> refer
>   avarage ==> average
>
> Just fix it.
>
> Signed-off-by: Jianyun Gao <jianyungao89@...il.com>
> ---
>  include/linux/delay.h         | 8 ++++----
>  kernel/time/posix-timers.c    | 2 +-
>  kernel/time/timer_migration.c | 4 ++--
>  3 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/include/linux/delay.h b/include/linux/delay.h
> index 89866bab100d..46412c00033a 100644
> --- a/include/linux/delay.h
> +++ b/include/linux/delay.h
> @@ -68,7 +68,7 @@ void usleep_range_state(unsigned long min, unsigned long max,
>   * @min:       Minimum time in microseconds to sleep
>   * @max:       Maximum time in microseconds to sleep
>   *
> - * For basic information please refere to usleep_range_state().
> + * For basic information please refer to usleep_range_state().
>   *
>   * The task will be in the state TASK_UNINTERRUPTIBLE during the sleep.
>   */
> @@ -82,10 +82,10 @@ static inline void usleep_range(unsigned long min, unsigned long max)
>   * @min:       Minimum time in microseconds to sleep
>   * @max:       Maximum time in microseconds to sleep
>   *
> - * For basic information please refere to usleep_range_state().
> + * For basic information please refer to usleep_range_state().
>   *
>   * The sleeping task has the state TASK_IDLE during the sleep to prevent
> - * contribution to the load avarage.
> + * contribution to the load average.
>   */
>  static inline void usleep_range_idle(unsigned long min, unsigned long max)
>  {
> @@ -96,7 +96,7 @@ static inline void usleep_range_idle(unsigned long min, unsigned long max)
>   * ssleep - wrapper for seconds around msleep
>   * @seconds:   Requested sleep duration in seconds
>   *
> - * Please refere to msleep() for detailed information.
> + * Please refer to msleep() for detailed information.
>   */
>  static inline void ssleep(unsigned int seconds)
>  {
> diff --git a/kernel/time/posix-timers.c b/kernel/time/posix-timers.c
> index aa3120104a51..36dbb8146517 100644
> --- a/kernel/time/posix-timers.c
> +++ b/kernel/time/posix-timers.c
> @@ -1242,7 +1242,7 @@ SYSCALL_DEFINE2(clock_adjtime, const clockid_t, which_clock,
>   *    sys_clock_settime(). The kernel internal timekeeping is always using
>   *    nanoseconds precision independent of the clocksource device which is
>   *    used to read the time from. The resolution of that device only
> - *    affects the presicion of the time returned by sys_clock_gettime().
> + *    affects the precision of the time returned by sys_clock_gettime().
>   *
>   * Returns:
>   *     0               Success. @tp contains the resolution
> diff --git a/kernel/time/timer_migration.c b/kernel/time/timer_migration.c
> index c0c54dc5314c..d4f4398dec50 100644
> --- a/kernel/time/timer_migration.c
> +++ b/kernel/time/timer_migration.c
> @@ -708,7 +708,7 @@ void tmigr_cpu_activate(void)
>  /*
>   * Returns true, if there is nothing to be propagated to the next level
>   *
> - * @data->firstexp is set to expiry of first gobal event of the (top level of
> + * @data->firstexp is set to expiry of first global event of the (top level of
>   * the) hierarchy, but only when hierarchy is completely idle.
>   *
>   * The child and group states need to be read under the lock, to prevent a race
> @@ -1621,7 +1621,7 @@ static void tmigr_connect_child_parent(struct tmigr_group *child,
>          *   created group (parent).
>          *
>          * * It is ensured that the child is active, as this setup path is
> -        *   executed in hotplug prepare callback. This is exectued by an
> +        *   executed in hotplug prepare callback. This is executed by an
>          *   already connected and !idle CPU. Even if all other CPUs go idle,
>          *   the CPU executing the setup will be responsible up to current top
>          *   level group. And the next time it goes inactive, it will release
> --
> 2.34.1
>