From: Wang Yan <wangyan01@kylinos.cn>
To: "Shuah Khan" <shuah@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Günther Noack" <gnoack@google.com>,
linux-security-module@vger.kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Wang Yan <wangyan01@kylinos.cn>
Subject: [PATCH 0/6] selftests: fix multiple spelling errors across submodules
Date: Wed, 1 Jul 2026 20:35:14 +0800 [thread overview]
Message-ID: <20260701123520.271580-1-wangyan01@kylinos.cn> (raw)
This series fixes trivial spelling typos in comments across multiple
selftests subdirectories. All changes are pure comment fixes, no
functional or logical change to any test logic.
Changes are split by subsystem for easier review and merging.
Please review.
Wang Yan (6):
selftests/arm64: fix spelling errors in comments
selftests/filesystems: fix spelling error in statmount test comment
selftests/ftrace: fix spelling error in poll test comment
selftests/kvm/x86: fix spelling error in xapic_ipi_test comment
selftests/landlock: fix spelling error in fs_test comment
selftests/powerpc/tm: fix spelling errors in comments
tools/testing/selftests/arm64/gcs/libc-gcs.c | 2 +-
tools/testing/selftests/arm64/pauth/pac.c | 2 +-
tools/testing/selftests/filesystems/statmount/statmount_test.c | 2 +-
tools/testing/selftests/ftrace/poll.c | 2 +-
tools/testing/selftests/kvm/x86/xapic_ipi_test.c | 2 +-
tools/testing/selftests/landlock/fs_test.c | 2 +-
tools/testing/selftests/powerpc/tm/tm-signal-msr-resv.c | 2 +-
tools/testing/selftests/powerpc/tm/tm-signal-stack.c | 2 +-
tools/testing/selftests/powerpc/tm/tm-tar.c | 2 +-
9 files changed, 9 insertions(+), 9 deletions(-)
--
2.25.1
next reply other threads:[~2026-07-01 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 12:35 Wang Yan [this message]
2026-07-01 12:35 ` [PATCH 5/6] selftests/landlock: fix spelling error in fs_test comment Wang Yan
2026-07-01 14:18 ` [PATCH 0/6] selftests: fix multiple spelling errors across submodules Sean Christopherson
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=20260701123520.271580-1-wangyan01@kylinos.cn \
--to=wangyan01@kylinos.cn \
--cc=gnoack@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=shuah@kernel.org \
/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