From: kernel test robot <lkp@intel.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
linux-doc@vger.kernel.org
Subject: [linux-next:master 13629/13985] htmldocs: Documentation/loongarch/introduction.rst:362: WARNING: duplicate label loongarch-references, other instance in Documentation/arch/loongarch/introduction.rst
Date: Wed, 6 Sep 2023 03:50:23 +0800 [thread overview]
Message-ID: <202309060352.2ZuAeYVF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: c50216cfa084d5eb67dc10e646a3283da1595bb6
commit: 2bf3c0292f35e84a2111e6e83f023c2690b25a71 [13629/13985] Merge patch series "RISC-V: Probe for misaligned access speed"
reproduce: (https://download.01.org/0day-ci/archive/20230906/202309060352.2ZuAeYVF-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309060352.2ZuAeYVF-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/loongarch/introduction.rst:362: WARNING: duplicate label loongarch-references, other instance in Documentation/arch/loongarch/introduction.rst
>> Documentation/translations/zh_CN/loongarch/introduction.rst:325: WARNING: duplicate label loongarch-references-zh_cn, other instance in Documentation/translations/zh_CN/arch/loongarch/introduction.rst
>> Documentation/translations/zh_CN/mips/booting.rst:14: WARNING: duplicate label cn_booting, other instance in Documentation/translations/zh_CN/arch/mips/booting.rst
>> Documentation/translations/zh_CN/mips/ingenic-tcu.rst:15: WARNING: duplicate label cn_ingenic-tcu, other instance in Documentation/translations/zh_CN/arch/mips/ingenic-tcu.rst
>> Documentation/bpf/instruction-set.rst: WARNING: document isn't included in any toctree
>> Documentation/hwmon/smm665.rst: WARNING: document isn't included in any toctree
>> Documentation/loongarch/index.rst: WARNING: document isn't included in any toctree
>> Documentation/mips/index.rst: WARNING: document isn't included in any toctree
>> Documentation/mm/frontswap.rst: WARNING: document isn't included in any toctree
>> Documentation/networking/device_drivers/ethernet/mellanox/mlx5/devlink.rst: WARNING: document isn't included in any toctree
>> Documentation/s390/index.rst: WARNING: document isn't included in any toctree
>> Documentation/translations/zh_CN/mm/frontswap.rst: WARNING: document isn't included in any toctree
vim +362 Documentation/loongarch/introduction.rst
0ea8ce61cb2c48 Huacai Chen 2022-05-31 360
0ea8ce61cb2c48 Huacai Chen 2022-05-31 361 References
0ea8ce61cb2c48 Huacai Chen 2022-05-31 @362 ==========
0ea8ce61cb2c48 Huacai Chen 2022-05-31 363
:::::: The code at line 362 was first introduced by commit
:::::: 0ea8ce61cb2c487e818c515f91329fa9972a7155 Documentation: LoongArch: Add basic documentations
:::::: TO: Huacai Chen <chenhuacai@loongson.cn>
:::::: CC: Huacai Chen <chenhuacai@loongson.cn>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-05 19:51 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=202309060352.2ZuAeYVF-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@rivosinc.com \
/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