From: kernel test robot <lkp@intel.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Jon Mason <jdmason@kudzu.us>,
linux-doc@vger.kernel.org
Subject: [linux-next:master 3587/7896] htmldocs: Documentation/PCI/endpoint/pci-vntb-function.rst:82: WARNING: Unexpected indentation.
Date: Tue, 5 Jul 2022 18:58:39 +0800 [thread overview]
Message-ID: <202207051821.3f0eRIsL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 2a2aa3f05338270aecbe2492fda910d6c17e0102
commit: 0c4b285d9636cc850f55151fa6a250dd131e5192 [3587/7896] Documentation: PCI: Add specification for the PCI vNTB function device
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/PCI/endpoint/pci-vntb-function.rst:82: WARNING: Unexpected indentation.
>> Documentation/PCI/endpoint/pci-vntb-howto.rst:131: WARNING: Title underline too short.
vim +82 Documentation/PCI/endpoint/pci-vntb-function.rst
60
61 It is appended after Config region.
62
63 +--------------------------------------------------+ Base
64 | |
65 | |
66 | |
67 | Common Config Register |
68 | |
69 | |
70 | |
71 +-----------------------+--------------------------+ Base + span_offset
72 | | |
73 | Peer Span Space | Span Space |
74 | | |
75 | | |
76 +-----------------------+--------------------------+ Base + span_offset
77 | | | + span_count * 4
78 | | |
79 | Span Space | Peer Span Space |
80 | | |
81 +-----------------------+--------------------------+
> 82 Virtual PCI Pcie Endpoint
83 NTB Driver NTB Driver
84
85
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-05 10:59 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=202207051821.3f0eRIsL-lkp@intel.com \
--to=lkp@intel.com \
--cc=Frank.Li@nxp.com \
--cc=jdmason@kudzu.us \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.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).