--- /dev/null
+From efbc6bd090f48ccf64f7a8dd5daea775821d57ec Mon Sep 17 00:00:00 2001
+From: Paolo Bonzini <pbonzini@redhat.com>
+Date: Fri, 27 Sep 2024 11:45:45 -0400
+Subject: Documentation: KVM: fix warning in "make htmldocs"
+
+From: Paolo Bonzini <pbonzini@redhat.com>
+
+commit efbc6bd090f48ccf64f7a8dd5daea775821d57ec upstream.
+
+The warning
+
+ Documentation/virt/kvm/locking.rst:31: ERROR: Unexpected indentation.
+
+is caused by incorrectly treating a line as the continuation of a paragraph,
+rather than as the first line in a bullet list.
+
+Fixed: 44d174596260 ("KVM: Use dedicated mutex to protect kvm_usage_count to avoid deadlock")
+Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ Documentation/virt/kvm/locking.rst | 1 +
+ 1 file changed, 1 insertion(+)
+
+--- a/Documentation/virt/kvm/locking.rst
++++ b/Documentation/virt/kvm/locking.rst
+@@ -25,6 +25,7 @@ The acquisition orders for mutexes are a
+ must not take either kvm->slots_lock or kvm->slots_arch_lock.
+
+ cpus_read_lock() vs kvm_lock:
++
+ - Taking cpus_read_lock() outside of kvm_lock is problematic, despite that
+ being the official ordering, as it is quite easy to unknowingly trigger
+ cpus_read_lock() while holding kvm_lock. Use caution when walking vm_list,