public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: Ziyu Chen <chenziyu@uniontech.com>
To: Christian Brauner <brauner@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	zhanjun@uniontech.com, niecheng1@uniontech.com,
	kernel@uniontech.com, Ziyu Chen <chenziyu@uniontech.com>,
	Cryolitia PukNgae <cryolitia@uniontech.com>
Subject: [PATCH v2] selftests/pidfd: fix typo in comment
Date: Wed, 21 Jan 2026 17:41:47 +0800	[thread overview]
Message-ID: <20260121094147.4187337-1-chenziyu@uniontech.com> (raw)
In-Reply-To: <20260121060333.4160937-1-chenziyu@uniontech.com>

Fix the typo "untill" → "until" in a comment in pidfd_info_test.c.

This typo is already listed in scripts/spelling.txt by commit
66b47b4a9dad ("checkpatch: look for common misspellings").

Suggested-by: Cryolitia PukNgae <cryolitia@uniontech.com>
Signed-off-by: Ziyu Chen <chenziyu@uniontech.com>
---
v2:
- Fix unintended whitespace removal in the comment ("we're killed").
 tools/testing/selftests/pidfd/pidfd_info_test.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/testing/selftests/pidfd/pidfd_info_test.c b/tools/testing/selftests/pidfd/pidfd_info_test.c
index 6571e04acd88..8bed951e06a0 100644
--- a/tools/testing/selftests/pidfd/pidfd_info_test.c
+++ b/tools/testing/selftests/pidfd/pidfd_info_test.c
@@ -229,7 +229,7 @@ static void *pidfd_info_pause_thread(void *arg)
 
 	close(ipc_socket);
 
-	/* Sleep untill we're killed. */
+	/* Sleep until we're killed. */
 	pause();
 	return NULL;
 }
-- 
2.20.1


  reply	other threads:[~2026-01-21  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21  6:03 [PATCH] selftests/pidfd: Fix comment typo already covered by spelling.txt Ziyu Chen
2026-01-21  9:41 ` Ziyu Chen [this message]
2026-01-21 17:58   ` [PATCH v2] selftests/pidfd: fix typo in comment Shuah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260121094147.4187337-1-chenziyu@uniontech.com \
    --to=chenziyu@uniontech.com \
    --cc=brauner@kernel.org \
    --cc=cryolitia@uniontech.com \
    --cc=kernel@uniontech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=niecheng1@uniontech.com \
    --cc=shuah@kernel.org \
    --cc=zhanjun@uniontech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox