[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87sema8yhy.fsf@trenco.lwn.net>
Date: Mon, 14 Apr 2025 11:05:29 -0600
From: Jonathan Corbet <corbet@....net>
To: "Xin Li (Intel)" <xin@...or.com>, kvm@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: pbonzini@...hat.com
Subject: Re: [PATCH v1 1/1] Documentation: kvm: Fix a section number
"Xin Li (Intel)" <xin@...or.com> writes:
> The previous section is 7.41, thus this should be 7.42.
>
> Signed-off-by: Xin Li (Intel) <xin@...or.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
Powered by blists - more mailing lists