From: SeongJae Park <sj@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: SeongJae Park <sjpark@amazon.de>,
damon@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-doc@vger.kernel.org
Subject: Re: [sj:damon/next 26/37] htmldocs: Documentation/admin-guide/mm/damon/guide.rst:5: WARNING: Duplicate explicit target name: "page".
Date: Sun, 30 Oct 2022 18:52:12 +0000 [thread overview]
Message-ID: <20221030185212.104281-1-sj@kernel.org> (raw)
In-Reply-To: <202210301953.0QNM3R4h-lkp@intel.com>
On Sun, 30 Oct 2022 19:48:49 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git damon/=
> next
> head: be45b44bd28cc8b20ccb1197147389e75d815e68
> commit: 1304ee0155423bb664d6b4342faa02765bf393bb [26/37] Docs/DAMON: Add mo=
> re DAMON docs for external DAMON-only html documents
> reproduce:
> # https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git/commit/?id=3D1304ee0155423bb664d6b4342faa02765bf393bb
> git remote add sj https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git
> git fetch --no-tags sj damon/next
> git checkout 1304ee0155423bb664d6b4342faa02765bf393bb
> 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>
Thank you, I fixed these and pushed[1,2]!
[1] https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git/commit/?h=damon/next&id=4e00b5e54958681516214cdb674160f7f8d0442c
[2] https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git/commit/?h=damon/next&id=458173b3a762f83527d35cff2ca2693bb17d7911
Thanks,
SJ
[...]
prev parent reply other threads:[~2022-10-30 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 11:48 [sj:damon/next 26/37] htmldocs: Documentation/admin-guide/mm/damon/guide.rst:5: WARNING: Duplicate explicit target name: "page" kernel test robot
2022-10-30 18:52 ` SeongJae Park [this message]
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=20221030185212.104281-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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 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.