From: kernel test robot <lkp@intel.com>
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org,
"Jonathan Corbet" <corbet@lwn.net>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Sunil V L" <sunilvl@ventanamicro.com>,
"Andrew Jones" <ajones@ventanamicro.com>,
"Palmer Dabbelt" <palmer@rivosinc.com>,
"Atish Patra" <atishp@rivosinc.com>,
"Song Shuai" <songshuaishuai@tinylab.org>,
"Randy Dunlap" <rdunlap@infradead.org>
Subject: [lwn:docs-next 37/49] htmldocs: Warning: Documentation/riscv/boot.rst references a file that doesn't exist: Documentation/arm/uefi.rst
Date: Tue, 15 Aug 2023 10:35:43 +0800 [thread overview]
Message-ID: <202308151010.JGqiPc9F-lkp@intel.com> (raw)
tree: git://git.lwn.net/linux.git docs-next
head: 90cd0c18573ad0583dec098a586f86d281947eb9
commit: e0bec22f06641e4a7ccd7fb1f8ed4588839b660b [37/49] Documentation: riscv: Add early boot document
reproduce: (https://download.01.org/0day-ci/archive/20230815/202308151010.JGqiPc9F-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/202308151010.JGqiPc9F-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: Documentation/riscv/boot.rst references a file that doesn't exist: Documentation/arm/uefi.rst
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-08-15 2:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 2:35 kernel test robot [this message]
2023-08-17 12:30 ` [lwn:docs-next 37/49] htmldocs: Warning: Documentation/riscv/boot.rst references a file that doesn't exist: Documentation/arm/uefi.rst Alexandre Ghiti
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=202308151010.JGqiPc9F-lkp@intel.com \
--to=lkp@intel.com \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=atishp@rivosinc.com \
--cc=bjorn@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@rivosinc.com \
--cc=rdunlap@infradead.org \
--cc=songshuaishuai@tinylab.org \
--cc=sunilvl@ventanamicro.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;
as well as URLs for NNTP newsgroup(s).