linux-kernel - [PATCH][next] selftests/futex: Fix spelling mistake "Succeffuly" -> "Successfully"

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>] [day] [month] [year] [list]

Message-ID: <20250715130627.1907017-1-colin.i.king@gmail.com>
Date: Tue, 15 Jul 2025 14:06:26 +0100
From: Colin Ian King <colin.i.king@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Darren Hart <dvhart@...radead.org>,
	Davidlohr Bueso <dave@...olabs.net>,
	André Almeida <andrealmeid@...lia.com>,
	Shuah Khan <shuah@...nel.org>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	linux-kselftest@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: [PATCH][next] selftests/futex: Fix spelling mistake "Succeffuly" -> "Successfully"

There is a spelling mistake in a ksft_exit_fail_msg message. Fix it.

Signed-off-by: Colin Ian King <colin.i.king@...il.com>
---
 tools/testing/selftests/futex/functional/futex_priv_hash.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/testing/selftests/futex/functional/futex_priv_hash.c b/tools/testing/selftests/futex/functional/futex_priv_hash.c
index a9cedc365102..aea001ac4946 100644
--- a/tools/testing/selftests/futex/functional/futex_priv_hash.c
+++ b/tools/testing/selftests/futex/functional/futex_priv_hash.c
@@ -122,7 +122,7 @@ static void futex_dummy_op(void)
 	}
 	ret = pthread_mutex_timedlock(&lock, &timeout);
 	if (ret == 0)
-		ksft_exit_fail_msg("Succeffuly locked an already locked mutex.\n");
+		ksft_exit_fail_msg("Successfully locked an already locked mutex.\n");
 
 	if (ret != ETIMEDOUT)
 		ksft_exit_fail_msg("pthread_mutex_timedlock() did not timeout: %d.\n", ret);
-- 
2.50.0