[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220407123327.159079-1-bagasdotme@gmail.com>
Date: Thu, 7 Apr 2022 19:33:27 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: linux-doc@...r.kernel.org
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, KVM <kvm@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Bagas Sanjaya <bagasdotme@...il.com>,
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>,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: [PATCH v2] 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")
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>
---
Changes since v1 [1]:
- Rebased on v5.18-rc1
- Address Fixes tag problems reported by Stephen Rothwell [2] by
removing date and quote the original commit
[1]: https://lore.kernel.org/linux-doc/20220403065735.23859-1-bagasdotme@gmail.com/
[2]: https://lore.kernel.org/linux-next/20220407074844.110f9285@canb.auug.org.au/
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 d13fa66004672c..85c7abc51af521 100644
--- a/Documentation/virt/kvm/api.rst
+++ b/Documentation/virt/kvm/api.rst
@@ -6190,6 +6190,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: 3123109284176b1532874591f7c81f3837bbdc17
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists