From: kernel test robot <lkp@intel.com>
To: Isaku Yamahata <isaku.yamahata@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: [intel-tdx:kvm-upstream-workaround 306/442] htmldocs: Documentation/virt/kvm/tdx-legacy-mmu.rst:49: WARNING: Unexpected indentation.
Date: Tue, 5 Jul 2022 15:56:44 +0800 [thread overview]
Message-ID: <202207051551.z6X8ExZg-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: 8af973ebaf30642129fc1ca63f155a469f9615ed
commit: b3b66d4ef5e175da9ce1ed41277130fee7cbdd84 [306/442] KVM: x86: design documentation on TDX support of x86 legacy KVM MMU
reproduce: make htmldocs
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> Documentation/virt/kvm/tdx-legacy-mmu.rst:49: WARNING: Unexpected indentation.
>> Documentation/virt/kvm/tdx-legacy-mmu.rst:50: WARNING: Block quote ends without a blank line; unexpected unindent.
>> Documentation/virt/kvm/tdx-legacy-mmu.rst:52: WARNING: Definition list ends without a blank line; unexpected unindent.
>> Documentation/virt/kvm/tdx-legacy-mmu.rst: WARNING: document isn't included in any toctree
vim +49 Documentation/virt/kvm/tdx-legacy-mmu.rst
44
45 (private EPT entry, shared EPT entry) =
46 (non-present, non-present): private mapping is allowed
47 (present, non-present): private mapping is mapped
48 (non-present | SPTE_SHARED_MASK, non-present):
> 49 shared mapping is allowed
> 50 (non-present | SPTE_SHARED_MASK, present):
51 shared mapping is mapped
> 52 (present, present): invalid combination
53
54
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-05 7:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202207051551.z6X8ExZg-lkp@intel.com \
--to=lkp@intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®