Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: David Gow <david@davidgow.net>
To: Jinseok Kim <always.starving0@gmail.com>, brendan.higgins@linux.dev
Cc: raemoar63@gmail.com, skhan@linuxfoundation.org,
	me@brighamcampbell.com, jkoolstra@xs4all.nl,
	linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
	linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] kunit: Fix spelling mistakes in comments and messages
Date: Sat, 2 May 2026 10:56:09 +0800	[thread overview]
Message-ID: <131e1ff1-4d29-4e45-8f85-33e2a8983b2b@davidgow.net> (raw)
In-Reply-To: <20260501162739.3861-1-always.starving0@gmail.com>

Le 02/05/2026 à 12:27 AM, Jinseok Kim a écrit :
> Fix two spelling mistakes in kunit tooling:
>    Bascially -> Basically
>    higer     -> higher
> 
> Signed-off-by: Jinseok Kim <always.starving0@gmail.com>
> ---

Thanks!

Reviewed-by: David Gow <david@davidgow.net>

Cheers,
-- David

>   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	other threads:[~2026-05-02  2:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 16:27 [PATCH] kunit: Fix spelling mistakes in comments and messages Jinseok Kim
2026-05-02  2:56 ` David Gow [this message]

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=131e1ff1-4d29-4e45-8f85-33e2a8983b2b@davidgow.net \
    --to=david@davidgow.net \
    --cc=always.starving0@gmail.com \
    --cc=brendan.higgins@linux.dev \
    --cc=jkoolstra@xs4all.nl \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=me@brighamcampbell.com \
    --cc=raemoar63@gmail.com \
    --cc=skhan@linuxfoundation.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