From: kernel test robot <lkp@intel.com>
To: Joel Fernandes <joelagnelf@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>,
linux-doc@vger.kernel.org
Subject: htmldocs: Documentation/gpu/nova/core/intr-ctrl.rst:88: WARNING: Inline substitution_reference start-string without end-string. [docutils]
Date: Sat, 02 May 2026 13:59:00 +0200 [thread overview]
Message-ID: <202605021358.ldpuPGZI-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Joel-Fernandes/rust-sync-completion-add-wait_for_completion_timeout/20260502-113009
head: 4e10e05ecde578bc23419ce04c62d82020b21d1a
commit: 4e10e05ecde578bc23419ce04c62d82020b21d1a gpu: nova-core: document INTR_CTRL interrupt tree
date: 8 hours ago
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux)
reproduce: (https://download.01.org/0day-ci/archive/20260502/202605021358.ldpuPGZI-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202605021358.ldpuPGZI-lkp@intel.com/
All warnings (new ones prefixed by >>):
Examples
~~~~~~~~ [docutils]
Documentation/gpu/nova/core/intr-ctrl.rst:110: ERROR: Unexpected indentation. [docutils]
>> Documentation/gpu/nova/core/intr-ctrl.rst:88: WARNING: Inline substitution_reference start-string without end-string. [docutils]
>> Documentation/gpu/nova/core/intr-ctrl.rst:111: WARNING: Line block ends without a blank line. [docutils]
>> Documentation/gpu/nova/core/intr-ctrl.rst:112: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/nova/core/intr-ctrl.rst:121: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/nova/core/intr-ctrl.rst:117: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/nova/core/intr-ctrl.rst:120: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
>> Documentation/gpu/nova/core/intr-ctrl.rst:121: WARNING: Blank line required after table. [docutils]
Documentation/gpu/nova/core/intr-ctrl.rst:122: WARNING: Line block ends without a blank line. [docutils]
Documentation/gpu/nova/core/intr-ctrl.rst:123: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/xe/xe_configfs:9: ./drivers/gpu/drm/xe/xe_configfs.c:27: ERROR: Unexpected section title.
vim +88 Documentation/gpu/nova/core/intr-ctrl.rst
86
87 It roughly looks like the following::
> 88 +--------------- Engine (CE, GR, NVDEC, ...) ---------------+
89 | |
90 | internal work completes |
91 | | |
92 | v |
93 | +-----------------------------------------+ |
94 | | INTR_CTRL(i): programmable register | |
95 | | (written once by GSP-RM at boot, | |
96 | | one such reg per engine) | |
97 | | | |
98 | | VECTOR = 200 (-> which leaf bit) | |
99 | | GFID = 0 (-> which function's | |
100 | | tree: 0=PF, N=VF) | |
101 | | CPU = 1 (-> copy to CPU tree?)| |
102 | | GSP = 0 (-> copy to GSP tree?)| |
103 | +--------------------+--------------------+ |
104 | | |
105 | engine builds | |
106 | interrupt ctrl | |
107 | command message | |
108 | (all2ctrl_intr_cmd) | |
109 +------------------------|----------------------------------+
110 |
> 111 v
> 112 +-----------------------------------------+
113 | Central INTR_CTRL block |
114 | |
115 | reads message; for the tree picked |
116 | by GFID, sets: |
117 | LEAF[ 200 / 32 ] = LEAF[6] |
118 | bit ( 200 % 32 ) = bit 8 |
119 | TOP subtree 3 = pending |
120 +--------------------+--------------------+
> 121 |
122 v
123 MSI to host (PF)
124
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-02 12:00 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=202605021358.ldpuPGZI-lkp@intel.com \
--to=lkp@intel.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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