From: kernel test robot <[email protected]>
To: Vikas Gupta <[email protected]>
Cc: [email protected], Ammar Faizi <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
[email protected], Jakub Kicinski <[email protected]>,
Andy Gospodarek <[email protected]>,
Jiri Pirko <[email protected]>,
[email protected]
Subject: [ammarfaizi2-block:netdev/net-next/main 16/29] htmldocs: Documentation/networking/devlink/devlink-selftests.rst: WARNING: document isn't included in any toctree
Date: Sat, 30 Jul 2022 04:37:02 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block netdev/net-next/main
head: 6957730e20389a63eb333afb6fcf38b45f549ea8
commit: 08f588fa301bef264576fc915da6bf31b585a824 [16/29] devlink: introduce framework for selftests
reproduce: make htmldocs
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>
All warnings (new ones prefixed by >>):
>> Documentation/networking/devlink/devlink-selftests.rst: WARNING: document isn't included in any toctree
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-29 20:37 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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