From: kernel test robot <lkp@intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Jason Gunthorpe <jgg@nvidia.com>,
linux-doc@vger.kernel.org
Subject: [jgunthorpe:iommufd 2/13] htmldocs: Documentation/userspace-api/iommufd.rst:55: (SEVERE/4) Unexpected section title or transition.
Date: Fri, 18 Mar 2022 09:14:26 +0800 [thread overview]
Message-ID: <202203180943.vNNAWkZa-lkp@intel.com> (raw)
tree: https://github.com/jgunthorpe/linux iommufd
head: 0ecea195175b25f110f9e0c66c94c5d00751a6ec
commit: a33afc78a9c19bc4e34f21acc8b521f125a0825f [2/13] iommufd: Overview documentation
reproduce: make htmldocs
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> Documentation/userspace-api/iommufd.rst:55: (SEVERE/4) Unexpected section title or transition.
vim +55 Documentation/userspace-api/iommufd.rst
54
> 55 _________________________________________________________
56 | iommufd |
57 | [1] |
58 | _________________ |
59 | | | |
60 | | | |
61 | | | |
62 | | | |
63 | | | |
64 | | | |
65 | | | [3] [2] |
66 | | | ____________ __________ |
67 | | IOAS |<--| |<------| | |
68 | | | |HW_PAGETABLE| | DEVICE | |
69 | | | |____________| |__________| |
70 | | | | | |
71 | | | | | |
72 | | | | | |
73 | | | | | |
74 | | | | | |
75 | |_________________| | | |
76 | | | | |
77 |_________|___________________|___________________|_______|
78 | | |
79 | _____v______ _______v_____
80 | PFN storage | | | |
81 |------------>|iommu_domain| |struct device|
82 |____________| |_____________|
83
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-18 1:15 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=202203180943.vNNAWkZa-lkp@intel.com \
--to=lkp@intel.com \
--cc=jgg@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=kevin.tian@intel.com \
--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®