From: kernel test robot <lkp@intel.com>
To: Kai Huang <kai.huang@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Isaku Yamahata <isaku.yamahata@intel.com>,
linux-doc@vger.kernel.org
Subject: [intel-tdx:kvm-upstream-workaround 130/411] htmldocs: Documentation/x86/tdx.rst:69: WARNING: Unexpected indentation.
Date: Sat, 9 Jul 2022 05:00:15 +0800 [thread overview]
Message-ID: <202207090435.U7loKEX3-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: 36253a6ed7e922a2e6888cde465578b98145404e
commit: 9b8d86c1e54a7018b65c179d4ede26ad89746c7c [130/411] Documentation/x86: Add documentation for TDX host support
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/x86/tdx.rst:69: WARNING: Unexpected indentation.
>> Documentation/x86/tdx.rst:70: WARNING: Block quote ends without a blank line; unexpected unindent.
vim +69 Documentation/x86/tdx.rst
66
67 ret = tdx_init();
68 if (ret)
> 69 goto no_tdx;
> 70 // TDX is ready to use
71
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-08 21:01 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=202207090435.U7loKEX3-lkp@intel.com \
--to=lkp@intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kai.huang@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