From: kernel test robot <lkp@intel.com>
To: Mike Rapoport <rppt@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"Mike Rapoport (IBM)" <rppt@kernel.org>
Subject: Re: [PATCH 1/2] docs/admin-guide/mm: remove useless markup
Date: Tue, 31 Jan 2023 16:10:22 +0800 [thread overview]
Message-ID: <202301311643.qUUNW7oe-lkp@intel.com> (raw)
In-Reply-To: <20230129075018.207678-2-rppt@kernel.org>
Hi Mike,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on lwn/docs-next]
[also build test WARNING on linus/master v6.2-rc6]
[cannot apply to akpm-mm/mm-everything next-20230131]
[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/Mike-Rapoport/docs-admin-guide-mm-remove-useless-markup/20230129-155123
base: git://git.lwn.net/linux.git docs-next
patch link: https://lore.kernel.org/r/20230129075018.207678-2-rppt%40kernel.org
patch subject: [PATCH 1/2] docs/admin-guide/mm: remove useless markup
reproduce:
# https://github.com/intel-lab-lkp/linux/commit/2e25559918a12ca208ce26ac82fc538d05dde591
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Mike-Rapoport/docs-admin-guide-mm-remove-useless-markup/20230129-155123
git checkout 2e25559918a12ca208ce26ac82fc538d05dde591
make menuconfig
# enable CONFIG_COMPILE_TEST, CONFIG_WARN_MISSING_DOCUMENTS, CONFIG_WARN_ABI_ERRORS
make htmldocs
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> Documentation/mm/physical_memory.rst:61: WARNING: undefined label: admin_guide_memory_hotplug (if the link has no caption the label must precede a section header)
>> Documentation/translations/zh_CN/admin-guide/mm/index.rst:24: WARNING: undefined label: mm_concepts (if the link has no caption the label must precede a section header)
>> Documentation/translations/zh_CN/mm/hugetlbfs_reserv.rst:18: WARNING: undefined label: hugetlbpage (if the link has no caption the label must precede a section header)
>> Documentation/translations/zh_CN/mm/numa.rst:76: WARNING: undefined label: numa_memory_policy (if the link has no caption the label must precede a section header)
vim +24 Documentation/translations/zh_CN/admin-guide/mm/index.rst
72e1bfd1b8e9d7 xu xin 2022-03-10 23
72e1bfd1b8e9d7 xu xin 2022-03-10 @24 Linux内存管理有它自己的术语,如果你还不熟悉它,请考虑阅读下面参考:
72e1bfd1b8e9d7 xu xin 2022-03-10 25 :ref:`Documentation/admin-guide/mm/concepts.rst <mm_concepts>`.
72e1bfd1b8e9d7 xu xin 2022-03-10 26
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-01-31 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 7:50 [PATCH 0/2] docs/mm: remove useless markup Mike Rapoport
2023-01-29 7:50 ` [PATCH 1/2] docs/admin-guide/mm: " Mike Rapoport
2023-01-31 8:10 ` kernel test robot [this message]
2023-01-29 7:50 ` [PATCH 2/2] docs/mm: " Mike Rapoport
2023-01-31 16:02 ` kernel test robot
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=202301311643.qUUNW7oe-lkp@intel.com \
--to=lkp@intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rppt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.