[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 4 Apr 2022 09:14:53 +0530
From: Anup Patel <anup@...infault.org>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Anup Patel <anup.patel@....com>,
Paolo Bonzini <pbonzini@...hat.com>,
Jonathan Corbet <corbet@....net>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
KVM General <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
linux-riscv <linux-riscv@...ts.infradead.org>
Subject: Re: [PATCH RESEND] Documentation: kvm: Add missing line break in api.rst
On Sun, Apr 3, 2022 at 12:28 PM Bagas Sanjaya <bagasdotme@...il.com> 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 <anup.patel@....com>
> Cc: Paolo Bonzini <pbonzini@...hat.com>
> Cc: Jonathan Corbet <corbet@....net>
> Cc: Paul Walmsley <paul.walmsley@...ive.com>
> Cc: Palmer Dabbelt <palmer@...belt.com>
> Cc: Albert Ou <aou@...s.berkeley.edu>
> Cc: kvm@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org
> Cc: linux-riscv@...ts.infradead.org
> Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
For KVM RISC-V related patches, please CC kvm-riscv@...ts.infradead.org
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
>
Powered by blists - more mailing lists