From: Soham Metha <sohammetha01@gmail.com>
To: linux-kselftest@vger.kernel.org
Cc: shuah@kernel.org, linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org,
Soham Metha <sohammetha01@gmail.com>
Subject: [PATCH 0/6] Kselftests: fix spelling mistakes
Date: Fri, 15 Aug 2025 05:38:58 +0530 [thread overview]
Message-ID: <20250815000859.112169-1-sohammetha01@gmail.com> (raw)
Used codespell to detect spelling mistakes across multiple tests
and fixed various simple typos found.
---
found/fixed the following typos:
> didnt't -> didn't
in `tools/testing/selftests/filesystems/statmount/statmount_test.c`
> add add -> add
> cannnot -> cannot
> fowarded -> forwarded
in `tools/testing/selftests/net/netfilter/nft_nat.sh`
> faile -> failed
in `tools/testing/selftests/ublk/test_common.sh`
> indicies -> indices
> requrired -> required
> guranteed -> guaranteed
in `tools/testing/selftests/kvm/riscv/sbi_pmu_test.c`
> avaialable -> available
in `tools/testing/selftests/kvm/s390/cpumodel_subfuncs_test.c`
> requries -> requires
in `tools/testing/selftests/safesetid/safesetid-test.c`
Soham Metha (6):
selftests: filesystems: statmout: fix spelling mistake in output
setftests: net: netfilter: fix spelling mistakes in output
selftests: ublk: fixed spelling mistake in output
selftests: kvm: riscv: fix spelling mistakes in comments
selftests: kvm: s390: fixed spelling mistake in output
selftests: net: tcp_ao: fix spelling mistake in comments
.../filesystems/statmount/statmount_test.c | 2 +-
.../testing/selftests/kvm/riscv/sbi_pmu_test.c | 10 +++++-----
.../kvm/s390/cpumodel_subfuncs_test.c | 2 +-
.../testing/selftests/net/netfilter/nft_nat.sh | 18 +++++++++---------
.../selftests/safesetid/safesetid-test.c | 2 +-
tools/testing/selftests/ublk/test_common.sh | 2 +-
6 files changed, 18 insertions(+), 18 deletions(-)
--
2.34.1
next reply other threads:[~2025-08-15 0:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 0:08 Soham Metha [this message]
2025-08-15 0:08 ` [PATCH 1/6] selftests: filesystems: statmout: fix spelling mistake in output Soham Metha
2025-08-15 0:17 ` [PATCH 2/6] setftests: net: netfilter: fix spelling mistakes " Soham Metha
2025-08-15 0:18 ` [PATCH 3/6] selftests: ublk: fixed spelling mistake " Soham Metha
2025-08-15 6:08 ` Ming Lei
2025-08-15 0:18 ` [PATCH 4/6] selftests: kvm: riscv: fix spelling mistakes in comments Soham Metha
2025-08-15 0:18 ` [PATCH 5/6] selftests: kvm: s390: fixed spelling mistake in output Soham Metha
2025-08-18 9:56 ` David Hildenbrand
2025-08-15 0:18 ` [PATCH 6/6] selftests: net: tcp_ao: fix spelling mistake in comments Soham Metha
2025-08-15 6:14 ` [PATCH 2/6] setftests: net: netfilter: fix spelling mistakes in output Florian Westphal
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=20250815000859.112169-1-sohammetha01@gmail.com \
--to=sohammetha01@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).