public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Xin Li (Intel)" <xin@zytor.com>,
	kvm@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: pbonzini@redhat.com
Subject: Re: [PATCH v1 1/1] Documentation: kvm: Fix a section number
Date: Mon, 14 Apr 2025 11:05:29 -0600	[thread overview]
Message-ID: <87sema8yhy.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250414165146.2279450-1-xin@zytor.com>

"Xin Li (Intel)" <xin@zytor.com> writes:

> The previous section is 7.41, thus this should be 7.42.
>
> Signed-off-by: Xin Li (Intel) <xin@zytor.com>
> ---
>  Documentation/virt/kvm/api.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index 47c7c3f92314..58478b470860 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -8478,7 +8478,7 @@ ENOSYS for the others.
>  When enabled, KVM will exit to userspace with KVM_EXIT_SYSTEM_EVENT of
>  type KVM_SYSTEM_EVENT_SUSPEND to process the guest suspend request.
>  
> -7.37 KVM_CAP_ARM_WRITABLE_IMP_ID_REGS
> +7.42 KVM_CAP_ARM_WRITABLE_IMP_ID_REGS
>  -------------------------------------

The fix seems fine but ... I have to ask ... do the section numbers buy
anything here?  We have a documentation system that can do nice
cross-references when needed, so I'm not sure that these numbers add
anything other than a bit of manual maintenance hassle.

Thanks,

jon

  reply	other threads:[~2025-04-14 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 16:51 [PATCH v1 1/1] Documentation: kvm: Fix a section number Xin Li (Intel)
2025-04-14 17:05 ` Jonathan Corbet [this message]
2025-04-14 17:21   ` Xin Li
2025-04-14 17:48     ` Jonathan Corbet
2025-04-14 17:59       ` Xin Li
2025-06-16  6:01 ` Xin Li

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=87sema8yhy.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=xin@zytor.com \
    /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