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 313/442] htmldocs: Documentation/ABI/testing/sysfs-firmware-tdx:2: WARNING: Unexpected indentation.
Date: Tue, 5 Jul 2022 20:50:46 +0800 [thread overview]
Message-ID: <202207052017.miU9soWY-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: 8af973ebaf30642129fc1ca63f155a469f9615ed
commit: 38171b7e61218ed34ba38f00c6503ffa3ee1a806 [313/442] x86/virt/tdx: Export TDX keyid number and status of TDX module via sysfs
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/ABI/testing/sysfs-firmware-tdx:2: WARNING: Unexpected indentation.
>> Documentation/ABI/testing/sysfs-firmware-tdx:2: WARNING: Block quote ends without a blank line; unexpected unindent.
>> Documentation/ABI/testing/sysfs-firmware-tdx:2: WARNING: Malformed table.
>> Documentation/ABI/testing/sysfs-firmware-tdx:22: WARNING: Blank line required after table.
>> Documentation/ABI/testing/sysfs-firmware-tdx:22: WARNING: Definition list ends without a blank line; unexpected unindent.
>> Documentation/ABI/testing/sysfs-firmware-tdx:1: WARNING: undefined label: abi_sys_firmware_tdx_tdx_module (if the link has no caption the label must precede a section header)
vim +2 Documentation/ABI/testing/sysfs-firmware-tdx
> 1 What: /sys/firmware/tdx/
> 2 Date: March 2022
3 KernelVersion: 5.17
4 Contact: Isaku Yamahata <isaku.yamahata@intel.com>, kvm@vger.kernel.org
5 Description:
6 Intel's Trust Domain Extensions (TDX) protect guest VMs from
7 malicious hosts and some physical attacks. This directory
8 represents the entry point directory for the TDX.
9
10 the TDX requires the TDX firmware to load into an isolated
11 memory region. It requires a two-step loading process. It uses
12 the first phase firmware loader (a.k.a NP-SEAMLDR) that loads
13 the next loader and the second phase firmware loader(a.k.a
14 P-SEAMLDR) that loads the TDX firmware(a.k.a the "TDX module").
15 =============== ================================================
16 keyid_num the number of SEAM keyid as an hexadecimal
17 number with the "0x" prefix.
18 =============== ================================================
19 Users: libvirt
20
21 What: /sys/firmware/tdx/tdx_module/
> 22 Date: March 2022
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-05 13:30 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=202207052017.miU9soWY-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;
as well as URLs for NNTP newsgroup(s).