From: kernel test robot <lkp@intel.com>
To: Yan Zhu <zhuyan2015@qq.com>,
corbet@lwn.net, alexs@kernel.org, si.yanteng@linux.dev,
kees@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, skhan@linuxfoundation.org,
dzm91@hust.edu.cn, tony.luck@intel.com, gpiccoli@igalia.com,
frederic@kernel.org, jani.nikula@intel.com, longman@redhat.com,
mchehab+huawei@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Yan Zhu <zhuyan2015@qq.com>
Subject: Re: [PATCH] docs/zh_CN: update admin-guide/index.rst translation
Date: Mon, 11 May 2026 10:39:44 +0200 [thread overview]
Message-ID: <202605111009.hlpiVkT6-lkp@intel.com> (raw)
In-Reply-To: <tencent_7ADF2D1EBD8EAD2028BC93BA7858EA655D0A@qq.com>
Hi Yan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on lwn/docs-next]
[also build test WARNING on linus/master v7.1-rc3 next-20260508]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Yan-Zhu/docs-zh_CN-update-admin-guide-index-rst-translation/20260511-102406
base: git://git.lwn.net/linux.git docs-next
patch link: https://lore.kernel.org/r/tencent_7ADF2D1EBD8EAD2028BC93BA7858EA655D0A%40qq.com
patch subject: [PATCH] docs/zh_CN: update admin-guide/index.rst translation
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/20260511/202605111009.hlpiVkT6-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/202605111009.hlpiVkT6-lkp@intel.com/
All warnings (new ones prefixed by >>):
Checksumming on output with GSO
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [docutils]
MAINTAINERS:40: WARNING: Inline strong start-string without end-string. [docutils]
>> Documentation/translations/zh_CN/admin-guide/index.rst:114: WARNING: toctree contains reference to nonexisting document 'translations/zh_CN/admin-guide/module-signing' [toc.not_readable]
Documentation/userspace-api/landlock:504: ./security/landlock/errata/abi-4.h:5: ERROR: Unexpected section title.
vim +114 Documentation/translations/zh_CN/admin-guide/index.rst
113
> 114 .. toctree::
115 :maxdepth: 1
116
117 cpu-load
118 mm/index
119 module-signing
120 numastat
121
122
123 Todolist:
124
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-05-11 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 6:48 [PATCH] docs/zh_CN: update admin-guide/index.rst translation Yan Zhu
2026-05-11 8:39 ` kernel test robot [this message]
2026-05-12 1:46 ` Dongliang Mu
2026-05-12 15:46 ` Yan Zhu
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=202605111009.hlpiVkT6-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=frederic@kernel.org \
--cc=gpiccoli@igalia.com \
--cc=jani.nikula@intel.com \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mchehab+huawei@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=tony.luck@intel.com \
--cc=zhuyan2015@qq.com \
/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