From: kernel test robot <lkp@intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org
Subject: [docs:docs-next 97/115] htmldocs: Documentation/core-api/mm-api:11: ./include/linux/uaccess.h:361: WARNING: Inline emphasis start-string without end-string. [docutils]
Date: Fri, 23 Oct 2026 11:44:51 +0200 [thread overview]
Message-ID: <202610231144.X9spCoJF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/docs/linux.git docs-next
head: f857ff5bf007f3394b704e200096571cbffdcc3a
commit: 131006cc650ccf5cbd2d6ac1953a263eb25756ea [97/115] docs: core-api: include documentation from linux/uaccess.h
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
docutils: docutils (Docutils 0.22.4, Python 3.13.5, on linux)
sphinx: sphinx-build 9.1.1
reproduce: (https://download.01.org/0day-ci/archive/20261023/202610231144.X9spCoJF-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/202610231144.X9spCoJF-lkp@intel.com/
All warnings (new ones prefixed by >>):
WARNING: ./include/linux/uaccess.h:532 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
* This is like copy_struct_from_user(), but the
WARNING: ./include/linux/uaccess.h:556 This comment starts with '/**', but isn't a kernel-doc comment. Refer to Documentation/doc-guide/kernel-doc.rst
* This is like copy_struct_to_user(), but the
Documentation/core-api/mm-api:11: ./include/linux/uaccess.h:363: ERROR: Unexpected indentation. [docutils]
>> Documentation/core-api/mm-api:11: ./include/linux/uaccess.h:361: WARNING: Inline emphasis start-string without end-string. [docutils]
Documentation/core-api/mm-api:11: ./include/linux/uaccess.h:373: ERROR: Unexpected indentation. [docutils]
>> Documentation/core-api/mm-api:11: ./include/linux/uaccess.h:376: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/core-api/mm-api:11: ./include/linux/uaccess.h:453: ERROR: Unexpected indentation. [docutils]
Documentation/core-api/mm-api:11: ./include/linux/uaccess.h:451: WARNING: Inline emphasis start-string without end-string. [docutils]
Documentation/core-api/mm-api:11: ./include/linux/uaccess.h:472: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
>> Documentation/core-api/mm-api:11: ./include/linux/uaccess.h:777: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
Documentation/core-api/mm-api:11: ./include/linux/uaccess.h:779: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/driver-api/basics:42: ./kernel/time/time.c:387: WARNING: Duplicate C declaration, also defined at driver-api/basics:436.
Declaration is '.. c:function:: unsigned int jiffies_to_msecs (const unsigned long j)'. [duplicate_declaration.c]
Documentation/driver-api/basics:42: ./kernel/time/time.c:410: WARNING: Duplicate C declaration, also defined at driver-api/basics:453.
Declaration is '.. c:function:: unsigned int jiffies_to_usecs (const unsigned long j)'. [duplicate_declaration.c]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-23 9:44 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=202610231144.X9spCoJF-lkp@intel.com \
--to=lkp@intel.com \
--cc=corbet@lwn.net \
--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