From: kernel test robot <lkp@intel.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: [intel-tdx:guest-attest 3/9] htmldocs: Documentation/x86/tdx.rst:275: WARNING: Field list ends without a blank line; unexpected unindent.
Date: Sun, 28 Aug 2022 12:12:30 +0800 [thread overview]
Message-ID: <202208281215.tlxpe8Ws-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git guest-attest
head: 32e0f882efcb0632adda39679d116f589f249d27
commit: c7d3f5519cee8f4cc42ed709450b48dd41876418 [3/9] Documentation/x86: Document TDX attestation process
reproduce:
# https://github.com/intel/tdx/commit/c7d3f5519cee8f4cc42ed709450b48dd41876418
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx guest-attest
git checkout c7d3f5519cee8f4cc42ed709450b48dd41876418
make menuconfig
# enable CONFIG_COMPILE_TEST, CONFIG_WARN_MISSING_DOCUMENTS, CONFIG_WARN_ABI_ERRORS
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:275: WARNING: Field list ends without a blank line; unexpected unindent.
vim +275 Documentation/x86/tdx.rst
266
267 Input parameters: Parameters passed to the IOCTL and related details.
268 Output : Details about output data and return value (with details
> 269 about the non common error values).
270
271 TDX_CMD_GET_REPORT
272 ------------------
273
274 :Input parameters: struct tdx_report_req
> 275 :Output : Upon successful execution, TDREPORT data is copied to
276 tdx_report_req.tdreport and returns 0 or returns
277 -EIO on TDCALL failure and standard error number on
278 other common failures.
279
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-28 4:12 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=202208281215.tlxpe8Ws-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@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