linux-kernel - [PATCH] Fixed typo in 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20230118220828.85115-1-semen.zhydenko@gmail.com>
Date:   Wed, 18 Jan 2023 23:08:28 +0100
From:   Semen Zhydenko <semen.zhydenko@...il.com>
To:     linux-kernel@...r.kernel.org, bagasdotme@...il.com
Cc:     Semen Zhydenko <semen.zhydenko@...il.com>
Subject: [PATCH] Fixed typo in comments

To change one typo in kernel/time/timer.c
Typo is "aquisition" proper spelling should be "acquisition".

Signed-off-by: Semen Zhydenko <semen.zhydenko@...il.com>
---
 kernel/time/timer.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/time/timer.c b/kernel/time/timer.c
index 63a8ce7177dd..6430c00b05a9 100644
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
@@ -1324,7 +1324,7 @@ static int __timer_delete(struct timer_list *timer, bool shutdown)
 	 * If @shutdown is set then the lock has to be taken whether the
 	 * timer is pending or not to protect against a concurrent rearm
 	 * which might hit between the lockless pending check and the lock
-	 * aquisition. By taking the lock it is ensured that such a newly
+	 * acquisition. By taking the lock it is ensured that such a newly
 	 * enqueued timer is dequeued and cannot end up with
 	 * timer->function == NULL in the expiry code.
 	 *
--
2.37.1 (Apple Git-137.1)