From: Chao Gao <chao.gao@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Yang Weijiang <weijiang.yang@intel.com>,
<oe-kbuild-all@lists.linux.dev>,
Sean Christopherson <seanjc@google.com>,
<linux-doc@vger.kernel.org>
Subject: Re: [sean-jc:q/cet 44/55] htmldocs: Documentation/virt/kvm/api.rst:2917: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Date: Wed, 10 Sep 2025 22:41:29 +0800 [thread overview]
Message-ID: <aMGOGVEvQz00Bm4J@intel.com> (raw)
In-Reply-To: <202509101552.nq7TgVwt-lkp@intel.com>
On Wed, Sep 10, 2025 at 03:45:08PM +0200, kernel test robot wrote:
>tree: https://github.com/sean-jc/linux q/cet
>head: 4a74767a033d98cd3e37a25c072d200d2d5545e2
>commit: 3ee447c42c42b6df04a5c8a0b9694bd0a5935078 [44/55] KVM: x86: Enable guest SSP read/write interface with new uAPIs
>reproduce: (https://download.01.org/0day-ci/archive/20250910/202509101552.nq7TgVwt-lkp@intel.com/reproduce)
>
>If you fix the issue in a separate patch/commit (i.e. not just a new version of
>the same patch/commit), kindly add following tags
>| Reported-by: kernel test robot <lkp@intel.com>
>| Closes: https://lore.kernel.org/oe-kbuild-all/202509101552.nq7TgVwt-lkp@intel.com/
>
>All warnings (new ones prefixed by >>):
>
> ERROR: Cannot find file ./include/linux/mutex.h
> WARNING: No kernel-doc for file ./include/linux/mutex.h
> ERROR: Cannot find file ./include/linux/fwctl.h
> WARNING: No kernel-doc for file ./include/linux/fwctl.h
> Documentation/virt/kvm/api.rst:2916: ERROR: Unexpected indentation. [docutils]
>>> Documentation/virt/kvm/api.rst:2917: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
>
>
>vim +2917 Documentation/virt/kvm/api.rst
>
> 2908
> 2909 0x9030 0000 0002 <reg:16>
> 2910
> 2911 x86 MSR registers have the following id bit patterns::
> 2912 0x2030 0002 <msr number:32>
> 2913
> 2914 Following are the KVM-defined registers for x86:
> 2915 ======================= ========= =============================================
> 2916 Encoding Register Description
>> 2917 ======================= ========= =============================================
> 2918 0x2030 0003 0000 0000 SSP Shadow Stack Pointer
> 2919 ======================= ========= =============================================
> 2920
A newline is needed before the table to suppress such an error:
diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
index 2b999408a768..dfb7a23020d1 100644
--- a/Documentation/virt/kvm/api.rst
+++ b/Documentation/virt/kvm/api.rst
@@ -2912,6 +2912,7 @@ x86 MSR registers have the following id bit patterns::
0x2030 0002 <msr number:32>
Following are the KVM-defined registers for x86:
+
======================= ========= =============================================
Encoding Register Description
======================= ========= =============================================
prev parent reply other threads:[~2025-09-10 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 13:45 [sean-jc:q/cet 44/55] htmldocs: Documentation/virt/kvm/api.rst:2917: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils] kernel test robot
2025-09-10 14:41 ` Chao Gao [this message]
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=aMGOGVEvQz00Bm4J@intel.com \
--to=chao.gao@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seanjc@google.com \
--cc=weijiang.yang@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;
as well as URLs for NNTP newsgroup(s).