From: SeongJae Park <sj@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: SeongJae Park <sjpark@amazon.de>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [sj:damon/next 17/20] htmldocs: Documentation/admin-guide/mm/damon/guide.rst:173: WARNING: unknown document: /vm/damon/api
Date: Mon, 4 Jul 2022 16:35:55 +0000 [thread overview]
Message-ID: <20220704163555.87880-1-sj@kernel.org> (raw)
In-Reply-To: <202207032102.FQn5Ryi7-lkp@intel.com>
On Sun, 3 Jul 2022 21:15:46 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git damon/=
> next
> head: 54aa71ecf6cac755c491a1992d83437cd2240311
> commit: e381a2734cd4250c0e3ab5f46cecc86ec67edb57 [17/20] Docs/DAMON: Add mo=
> re 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:173: WARNING: unknown docum=
> ent: /vm/damon/api
>
> vim +173 Documentation/admin-guide/mm/damon/guide.rst
>
> 172
> > 173 If you are a kernel space programmer, writing kernel space DAMON applications
> 174 using the API (refer to the :doc:`/vm/damon/api` for more detail) would be an
> 175 option.
> 176
> 177
Thank you for finding this issue! I fixed this with below change.
diff --git a/Documentation/admin-guide/mm/damon/guide.rst b/Documentation/admin-guide/mm/damon/guide.rst
index a014cb99a116..e1eb92c61499 100644
--- a/Documentation/admin-guide/mm/damon/guide.rst
+++ b/Documentation/admin-guide/mm/damon/guide.rst
@@ -171,7 +171,7 @@ applies complex optimizations itself. Using this, you can make more creative
and wise optimizations.
If you are a kernel space programmer, writing kernel space DAMON applications
-using the API (refer to the :doc:`/vm/damon/api` for more detail) would be an
+using the API (refer to the :doc:`/mm/damon/api` for more detail) would be an
option.
Please note that the issue is made by a commit that only for DAMON hacking
tree, not for the mainline or other trees. So the patch wouldn't be submitted
to other mailing lists.
Thanks,
SJ
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
>
prev parent reply other threads:[~2022-07-04 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 13:15 [sj:damon/next 17/20] htmldocs: Documentation/admin-guide/mm/damon/guide.rst:173: WARNING: unknown document: /vm/damon/api kernel test robot
2022-07-04 16:35 ` 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=20220704163555.87880-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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).