From: kernel test robot <[email protected]>
To: Ammar Faizi <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Cc: [email protected]
Subject: [ammarfaizi2-block:google/android/kernel/common/android12-kiwi-5.10 212/9999] htmldocs: Warning: Documentation/filesystems/incfs.rst references a file that doesn't exist: Documentation/ABI/testing/sys-fs-incfs
Date: Tue, 20 Sep 2022 17:54:44 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android12-kiwi-5.10
head: edf4da79d443f97049926ace891b5d6d235f7539
commit: 44ffa6511050005dc724d04297a15f7b32fec8af [212/9999] ANDROID: Incremental fs: Add status to sysfs
reproduce:
# https://github.com/ammarfaizi2/linux-block/commit/44ffa6511050005dc724d04297a15f7b32fec8af
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android12-kiwi-5.10
git checkout 44ffa6511050005dc724d04297a15f7b32fec8af
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 <[email protected]>
All warnings (new ones prefixed by >>):
>> Warning: Documentation/filesystems/incfs.rst references a file that doesn't exist: Documentation/ABI/testing/sys-fs-incfs
>> Documentation/filesystems/incfs.rst:24: WARNING: Unexpected indentation.
>> Documentation/filesystems/incfs.rst:31: WARNING: Block quote ends without a blank line; unexpected unindent.
>> Documentation/filesystems/incfs.rst: WARNING: document isn't included in any toctree
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-20 9:55 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] \
/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