[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <175844197200.709179.14745138242148511323.tip-bot2@tip-bot2>
Date: Sun, 21 Sep 2025 08:06:11 -0000
From: "tip-bot2 for Haofeng Li" <tip-bot2@...utronix.de>
To: linux-tip-commits@...r.kernel.org
Cc: Haofeng Li <lihaofeng@...inos.cn>, Thomas Gleixner <tglx@...utronix.de>,
x86@...nel.org, linux-kernel@...r.kernel.org
Subject: [tip: timers/core] time: Fix spelling mistakes in comments
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 391253b25f078d2fe5657a1dedd360396d186407
Gitweb: https://git.kernel.org/tip/391253b25f078d2fe5657a1dedd360396d186407
Author: Haofeng Li <lihaofeng@...inos.cn>
AuthorDate: Wed, 10 Sep 2025 17:37:03 +08:00
Committer: Thomas Gleixner <tglx@...utronix.de>
CommitterDate: Sun, 21 Sep 2025 10:02:02 +02:00
time: Fix spelling mistakes in comments
Correct several typos found in comments across various files in the
kernel/time directory.
No functional changes are introduced by these corrections.
Signed-off-by: Haofeng Li <lihaofeng@...inos.cn>
Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
---
kernel/time/alarmtimer.c | 2 +-
kernel/time/clocksource.c | 2 +-
kernel/time/hrtimer.c | 2 +-
kernel/time/posix-timers.c | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/time/alarmtimer.c b/kernel/time/alarmtimer.c
index 577f0e6..069d93b 100644
--- a/kernel/time/alarmtimer.c
+++ b/kernel/time/alarmtimer.c
@@ -35,7 +35,7 @@
/**
* struct alarm_base - Alarm timer bases
- * @lock: Lock for syncrhonized access to the base
+ * @lock: Lock for synchronized access to the base
* @timerqueue: Timerqueue head managing the list of events
* @get_ktime: Function to read the time correlating to the base
* @get_timespec: Function to read the namespace time correlating to the base
diff --git a/kernel/time/clocksource.c b/kernel/time/clocksource.c
index 3edb01d..a1890a0 100644
--- a/kernel/time/clocksource.c
+++ b/kernel/time/clocksource.c
@@ -144,7 +144,7 @@ static u64 suspend_start;
* Default for maximum permissible skew when cs->uncertainty_margin is
* not specified, and the lower bound even when cs->uncertainty_margin
* is specified. This is also the default that is used when registering
- * clocks with unspecifed cs->uncertainty_margin, so this macro is used
+ * clocks with unspecified cs->uncertainty_margin, so this macro is used
* even in CONFIG_CLOCKSOURCE_WATCHDOG=n kernels.
*/
#define WATCHDOG_MAX_SKEW (MAX_SKEW_USEC * NSEC_PER_USEC)
diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c
index f383df2..7e7b2b4 100644
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -201,7 +201,7 @@ static bool hrtimer_suitable_target(struct hrtimer *timer, struct hrtimer_clock_
/*
* The offline local CPU can't be the default target if the
* next remote target event is after this timer. Keep the
- * elected new base. An IPI will we issued to reprogram
+ * elected new base. An IPI will be issued to reprogram
* it as a last resort.
*/
if (!hrtimer_base_is_online(this_cpu_base))
diff --git a/kernel/time/posix-timers.c b/kernel/time/posix-timers.c
index 2741f37..aa31201 100644
--- a/kernel/time/posix-timers.c
+++ b/kernel/time/posix-timers.c
@@ -534,7 +534,7 @@ static int do_timer_create(clockid_t which_clock, struct sigevent *event,
goto out;
}
/*
- * After succesful copy out, the timer ID is visible to user space
+ * After successful copy out, the timer ID is visible to user space
* now but not yet valid because new_timer::signal low order bit is 1.
*
* Complete the initialization with the clock specific create
Powered by blists - more mailing lists