From: Randy Dunlap <rdunlap@infradead.org>
To: Fuad Tabba <fuad.tabba@linux.dev>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Huacai Chen <chenhuacai@kernel.org>,
linux-mips@vger.kernel.org, Will Deacon <will@kernel.org>,
Fuad Tabba <tabba@google.com>
Subject: Re: [PATCH 4/7] Documentation: KVM: Drop the stale number of vCPU request flags
Date: Sun, 15 Nov 2026 17:39:43 -0800 [thread overview]
Message-ID: <f4063ec4-2f1e-40b4-bcfb-83c3caf98cb5@infradead.org> (raw)
In-Reply-To: <20261111085448.1130701-5-fuad.tabba@linux.dev>
On 11/11/26 12:54 AM, Fuad Tabba wrote:
> vcpu-requests.rst states that only two request flags are defined, but
> KVM_REQUEST_NO_ACTION is a third. Drop the number.
>
> Signed-off-by: Fuad Tabba <fuad.tabba@linux.dev>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/virt/kvm/vcpu-requests.rst | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/Documentation/virt/kvm/vcpu-requests.rst b/Documentation/virt/kvm/vcpu-requests.rst
> index 06718b9bc9597..eedf338d47d6a 100644
> --- a/Documentation/virt/kvm/vcpu-requests.rst
> +++ b/Documentation/virt/kvm/vcpu-requests.rst
> @@ -141,8 +141,7 @@ KVM_REQUEST_MASK
>
> VCPU requests should be masked by KVM_REQUEST_MASK before using them with
> bitops. This is because only the lower 8 bits are used to represent the
> -request's number. The upper bits are used as flags. Currently only two
> -flags are defined.
> +request's number. The upper bits are used as flags.
>
> VCPU Request Flags
> ------------------
--
~Randy
next prev parent reply other threads:[~2026-11-16 1:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 8:54 [PATCH 0/7] KVM: Documentation and comment fixes Fuad Tabba
2026-11-11 8:54 ` [PATCH 1/7] Documentation: KVM: Fix references to non-existent identifiers Fuad Tabba
2026-11-16 1:30 ` Randy Dunlap
2026-11-11 8:54 ` [PATCH 2/7] Documentation: KVM: Fix lock names and a lock type in locking.rst Fuad Tabba
2026-11-11 8:54 ` [PATCH 3/7] Documentation: KVM: Fix the function that implements halt polling Fuad Tabba
2026-11-11 8:54 ` [PATCH 4/7] Documentation: KVM: Drop the stale number of vCPU request flags Fuad Tabba
2026-11-16 1:39 ` Randy Dunlap [this message]
2026-11-11 8:54 ` [PATCH 5/7] KVM: Fix comments that refer to non-existent identifiers Fuad Tabba
2026-11-11 21:31 ` Randy Dunlap
2026-11-11 8:54 ` [PATCH 6/7] KVM: Fix the range of reserved arch-independent request bits Fuad Tabba
2026-11-11 8:54 ` [PATCH 7/7] KVM: Fix typos in comments Fuad Tabba
2026-11-11 17:05 ` Randy Dunlap
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=f4063ec4-2f1e-40b4-bcfb-83c3caf98cb5@infradead.org \
--to=rdunlap@infradead.org \
--cc=borntraeger@linux.ibm.com \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=frankja@linux.ibm.com \
--cc=fuad.tabba@linux.dev \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tabba@google.com \
--cc=will@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
all inboxes | Powered by JetHome®