All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Piotr Zarycki <piotr.zarycki@gmail.com>,
	seanjc@google.com, pbonzini@redhat.com
Cc: shuah@kernel.org, kvm@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Piotr Zarycki <piotr.zarycki@gmail.com>
Subject: Re: [PATCH] KVM: selftests: Fix typo in comment in hyperv_features.c
Date: Tue, 28 Apr 2026 11:26:45 +0200	[thread overview]
Message-ID: <87v7dbl9ka.fsf@redhat.com> (raw)
In-Reply-To: <20260428083037.1926902-1-piotr.zarycki@gmail.com>

Piotr Zarycki <piotr.zarycki@gmail.com> writes:

> Fix a typo in a comment: 'vailable' -> 'available'.
>
> Signed-off-by: Piotr Zarycki <piotr.zarycki@gmail.com>
> ---
>  tools/testing/selftests/kvm/x86/hyperv_features.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/kvm/x86/hyperv_features.c b/tools/testing/selftests/kvm/x86/hyperv_features.c
> index 130b9ce7e5dd..f943c748f9ff 100644
> --- a/tools/testing/selftests/kvm/x86/hyperv_features.c
> +++ b/tools/testing/selftests/kvm/x86/hyperv_features.c
> @@ -457,7 +457,7 @@ static void guest_test_msrs_access(void)
>  			msr->fault_expected = true;
>  			break;
>  		case 45:
> -			/* MSR is vailable when CPUID feature bit is set */
> +			/* MSR is available when CPUID feature bit is set */
>  			if (!has_invtsc)
>  				goto next_stage;
>  			vcpu_set_cpuid_feature(vcpu, HV_ACCESS_TSC_INVARIANT);

Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>

Thanks!

-- 
Vitaly


  reply	other threads:[~2026-04-28  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  8:30 [PATCH] KVM: selftests: Fix typo in comment in hyperv_features.c Piotr Zarycki
2026-04-28  9:26 ` Vitaly Kuznetsov [this message]
2026-05-19  0:40 ` 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=87v7dbl9ka.fsf@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=piotr.zarycki@gmail.com \
    --cc=seanjc@google.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.