2022-04-04 23:37:24

by Bagas Sanjaya

[permalink] [raw]
Subject: [PATCH RESEND] Documentation: kvm: Add missing line break in api.rst

Add missing line break separator between literal block and description
of KVM_EXIT_RISCV_SBI.

This fixes:
</path/to/linux>/Documentation/virt/kvm/api.rst:6118: WARNING: Literal block ends without a blank line; unexpected unindent.

Fixes: da40d85805937d (RISC-V: KVM: Document RISC-V specific parts of KVM API, 2021-09-27)
Cc: Anup Patel <[email protected]>
Cc: Paolo Bonzini <[email protected]>
Cc: Jonathan Corbet <[email protected]>
Cc: Paul Walmsley <[email protected]>
Cc: Palmer Dabbelt <[email protected]>
Cc: Albert Ou <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Signed-off-by: Bagas Sanjaya <[email protected]>
---
Documentation/virt/kvm/api.rst | 1 +
1 file changed, 1 insertion(+)

diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
index 9f3172376ec3a6..a529f94b61edcd 100644
--- a/Documentation/virt/kvm/api.rst
+++ b/Documentation/virt/kvm/api.rst
@@ -6115,6 +6115,7 @@ Valid values for 'type' are:
unsigned long args[6];
unsigned long ret[2];
} riscv_sbi;
+
If exit reason is KVM_EXIT_RISCV_SBI then it indicates that the VCPU has
done a SBI call which is not handled by KVM RISC-V kernel module. The details
of the SBI call are available in 'riscv_sbi' member of kvm_run structure. The

base-commit: f443e374ae131c168a065ea1748feac6b2e76613
--
An old man doll... just what I always wanted! - Clara


2022-04-05 02:21:26

by Anup Patel

[permalink] [raw]
Subject: Re: [PATCH RESEND] Documentation: kvm: Add missing line break in api.rst

On Sun, Apr 3, 2022 at 12:28 PM Bagas Sanjaya <[email protected]> wrote:
>
> Add missing line break separator between literal block and description
> of KVM_EXIT_RISCV_SBI.
>
> This fixes:
> </path/to/linux>/Documentation/virt/kvm/api.rst:6118: WARNING: Literal block ends without a blank line; unexpected unindent.
>
> Fixes: da40d85805937d (RISC-V: KVM: Document RISC-V specific parts of KVM API, 2021-09-27)
> Cc: Anup Patel <[email protected]>
> Cc: Paolo Bonzini <[email protected]>
> Cc: Jonathan Corbet <[email protected]>
> Cc: Paul Walmsley <[email protected]>
> Cc: Palmer Dabbelt <[email protected]>
> Cc: Albert Ou <[email protected]>
> Cc: [email protected]
> Cc: [email protected]
> Cc: [email protected]
> Signed-off-by: Bagas Sanjaya <[email protected]>

For KVM RISC-V related patches, please CC [email protected]

Otherwise, this looks good to me. I have queued this for RC fixes.

Thanks,
Anup

> ---
> Documentation/virt/kvm/api.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
> index 9f3172376ec3a6..a529f94b61edcd 100644
> --- a/Documentation/virt/kvm/api.rst
> +++ b/Documentation/virt/kvm/api.rst
> @@ -6115,6 +6115,7 @@ Valid values for 'type' are:
> unsigned long args[6];
> unsigned long ret[2];
> } riscv_sbi;
> +
> If exit reason is KVM_EXIT_RISCV_SBI then it indicates that the VCPU has
> done a SBI call which is not handled by KVM RISC-V kernel module. The details
> of the SBI call are available in 'riscv_sbi' member of kvm_run structure. The
>
> base-commit: f443e374ae131c168a065ea1748feac6b2e76613
> --
> An old man doll... just what I always wanted! - Clara
>