From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Isaku Yamahata <isaku.yamahata@intel.com>,
Xiaoyao Li <xiaoyao.li@intel.com>,
Yu Zhang <yu.c.zhang@linux.intel.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH v2 3/3] Documentation: kvm: enclose the final closing brace in code block
Date: Wed, 17 Aug 2022 19:48:37 +0700 [thread overview]
Message-ID: <20220817124837.422695-4-bagasdotme@gmail.com> (raw)
In-Reply-To: <20220817124837.422695-1-bagasdotme@gmail.com>
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(-)
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)
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-08-17 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 12:48 [PATCH v2 0/3] Documentation fixes for kvm-upstream-workaround Bagas Sanjaya
2022-08-17 12:48 ` [PATCH v2 1/3] Documentation: ABI: tdx: fix formatting in ABI documentation Bagas Sanjaya
2022-08-17 12:48 ` [PATCH v2 2/3] Documentation: ABI: tdx: grammar improv Bagas Sanjaya
2022-08-17 12:48 ` Bagas Sanjaya [this message]
2022-08-23 5:57 ` [PATCH v2 0/3] Documentation fixes for kvm-upstream-workaround Isaku Yamahata
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220817124837.422695-4-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=chao.p.peng@linux.intel.com \
--cc=corbet@lwn.net \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pbonzini@redhat.com \
--cc=xiaoyao.li@intel.com \
--cc=yu.c.zhang@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox