From: kernel test robot <lkp@intel.com>
To: SeongJae Park <sjpark@amazon.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: [sj:damon/next 23/25] htmldocs: Documentation/admin-guide/mm/damon/guide.rst:5: WARNING: Duplicate explicit target name: "page".
Date: Tue, 26 Jul 2022 15:37:34 +0800 [thread overview]
Message-ID: <202207261536.B9ECWh72-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git damon/next
head: 7b095128a1a8d7cd001d16012bd33216b7c89b6c
commit: e3d45147e4fb374314d08e0028560463a7da232e [23/25] Docs/DAMON: Add more docs -next doc
reproduce: 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/admin-guide/mm/damon/guide.rst:5: WARNING: Duplicate explicit target name: "page".
>> Documentation/mm/damon/eval.rst:81: WARNING: Footnote is not referenced.
vim +/page +5 Documentation/admin-guide/mm/damon/guide.rst
2
3 ==================
4 Optimization Guide
> 5 ==================
6
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-26 7:38 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=202207261536.B9ECWh72-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjpark@amazon.de \
/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;
as well as URLs for NNTP newsgroup(s).