| Message ID | 20220817124837.422695-4-bagasdotme@gmail.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | Documentation fixes for kvm-upstream-workaround | expand |
diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst index d9d43078080030..4acf4d1c95c099 100644 --- a/Documentation/virt/kvm/api.rst +++ b/Documentation/virt/kvm/api.rst @@ -1359,7 +1359,7 @@ yet and must be cleared on entry. __u32 private_fd; __u32 pad1; __u64 pad2[14]; -}; + }; /\* for kvm_memory_region::flags \*/ #define KVM_MEM_LOG_DIRTY_PAGES (1UL << 0)
Sphinx reported literal block warning: Documentation/virt/kvm/api.rst:1362: WARNING: Literal block ends without a blank line; unexpected unindent. The warning is caused by the final closing brace in KVM_SET_USER_MEMORY_REGION struct definition is not indented as literal code block. Indent the closing brace to fix the warning. Link: https://lore.kernel.org/linux-doc/202208171109.lCfseeP6-lkp@intel.com/ Fixes: bb90daae9d7551 ("KVM: Extend the memslot to support fd-based private memory") Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com> --- Documentation/virt/kvm/api.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)