From: kernel test robot <lkp@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: kbuild-all@lists.01.org,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [djwong-xfs:vectorized-scrub 14/368] htmldocs: Documentation/filesystems/xfs-online-fsck-design.rst:822: WARNING: Duplicate explicit target name: "inode".
Date: Sun, 10 Jul 2022 08:52:19 +0800 [thread overview]
Message-ID: <202207100833.M6QSi3IA-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git vectorized-scrub
head: 569bd1ce4bb5c53a1b892fbe6d99693bf637063b
commit: 4dda10b2ba91b4d387f520a27cbd909d1d56374e [14/368] xfs: document technical aspects of kernel space file repair code
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/filesystems/xfs-online-fsck-design.rst:822: WARNING: Duplicate explicit target name: "inode".
vim +/inode +822 Documentation/filesystems/xfs-online-fsck-design.rst
08025a5b429713 Darrick J. Wong 2022-06-10 820
08025a5b429713 Darrick J. Wong 2022-06-10 821 Kernel Algorithms and Data Structures
08025a5b429713 Darrick J. Wong 2022-06-10 @822 =====================================
08025a5b429713 Darrick J. Wong 2022-06-10 823
:::::: The code at line 822 was first introduced by commit
:::::: 08025a5b429713a0fbbbe9747c496d3de200d0ce xfs: document technical aspects of kernel space metadata repair code
:::::: TO: Darrick J. Wong <djwong@kernel.org>
:::::: CC: Darrick J. Wong <djwong@kernel.org>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-10 0:52 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=202207100833.M6QSi3IA-lkp@intel.com \
--to=lkp@intel.com \
--cc=darrick.wong@oracle.com \
--cc=djwong@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®