From: kernel test robot <lkp@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Luca Coelho <luciano.coelho@intel.com>,
linux-doc@vger.kernel.org
Subject: [linux-next:master 379/5284] htmldocs: Documentation/gpu/rfc/i915_scheduler.rst:138: WARNING: Unknown directive type "c:namespace-push".
Date: Sun, 30 Jul 2023 19:00:56 +0800 [thread overview]
Message-ID: <202307301850.i9xFNWT6-lkp@intel.com> (raw)
Hi Jani,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: d7b3af5a77e8d8da28f435f313e069aea5bcf172
commit: f6757dfcfde722fdeaee371b66f63d7eb61dd7e4 [379/5284] drm/doc: fix duplicate declaration warning
reproduce: (https://download.01.org/0day-ci/archive/20230730/202307301850.i9xFNWT6-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/202307301850.i9xFNWT6-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/gpu/rfc/i915_scheduler.rst:138: WARNING: Unknown directive type "c:namespace-push".
>> Documentation/gpu/rfc/i915_scheduler.rst:143: WARNING: Unknown directive type "c:namespace-pop".
vim +138 Documentation/gpu/rfc/i915_scheduler.rst
137
> 138 .. c:namespace-push:: rfc
139
140 .. kernel-doc:: include/uapi/drm/i915_drm.h
141 :functions: i915_context_engines_parallel_submit
142
> 143 .. c:namespace-pop::
144
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-30 11:01 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=202307301850.i9xFNWT6-lkp@intel.com \
--to=lkp@intel.com \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luciano.coelho@intel.com \
--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