[PATCH] kunit: Fix spelling mistakes in comments and messages

0 views
Skip to first unread message

Jinseok Kim

unread,
12:28 PM (8 hours ago) 12:28 PM
to brendan...@linux.dev, da...@davidgow.net, raem...@gmail.com, sk...@linuxfoundation.org, m...@brighamcampbell.com, jkoo...@xs4all.nl, linux-k...@vger.kernel.org, kuni...@googlegroups.com, linux-...@vger.kernel.org, linux-kern...@lists.linux.dev
Fix two spelling mistakes in kunit tooling:
Bascially -> Basically
higer -> higher

Signed-off-by: Jinseok Kim <always.s...@gmail.com>
---
tools/testing/kunit/kunit_kernel.py | 2 +-
tools/testing/kunit/kunit_parser.py | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/testing/kunit/kunit_kernel.py b/tools/testing/kunit/kunit_kernel.py
index 2869fcb19..58557c47d 100644
--- a/tools/testing/kunit/kunit_kernel.py
+++ b/tools/testing/kunit/kunit_kernel.py
@@ -218,7 +218,7 @@ def _get_qemu_ops(config_path: str,
# exists (I learned this through experimentation and could not find it
# anywhere in the Python documentation).
#
- # Bascially, we completely ignore the actual file location of the config
+ # Basically, we completely ignore the actual file location of the config
# we are loading and just tell Python that the module lives in the
# QEMU_CONFIGS_DIR for import purposes regardless of where it actually
# exists as a file.
diff --git a/tools/testing/kunit/kunit_parser.py b/tools/testing/kunit/kunit_parser.py
index 1c61a0ed7..0e1d2f498 100644
--- a/tools/testing/kunit/kunit_parser.py
+++ b/tools/testing/kunit/kunit_parser.py
@@ -268,7 +268,7 @@ def check_version(version_num: int, accepted_versions: List[int],
if version_num < min(accepted_versions):
test.add_error(printer, f'{version_type} version lower than expected!')
elif version_num > max(accepted_versions):
- test.add_error(printer, f'{version_type} version higer than expected!')
+ test.add_error(printer, f'{version_type} version higher than expected!')

def parse_ktap_header(lines: LineStream, test: Test, printer: Printer) -> bool:
"""
--
2.43.0
Reply all
Reply to author
Forward
0 new messages