From: kernel test robot <lkp@intel.com>
To: William Zhang <william.zhang@broadcom.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-spi@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
linux-doc@vger.kernel.org
Subject: [broonie-spi:for-next 43/43] htmldocs: Warning: MAINTAINERS references a file that doesn't exist: Documentation/devicetree/bindings/spi/brcm,bcm63xx-hsspi-peripheral-props.yaml
Date: Sun, 12 Feb 2023 18:19:42 +0800 [thread overview]
Message-ID: <202302121840.GtduUT37-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
head: 80323599e33f9c19287a1a3707481fb157b27052
commit: 80323599e33f9c19287a1a3707481fb157b27052 [43/43] MAINTAINERS: Add entry for Broadcom Broadband SoC HS SPI drivers
reproduce:
# https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git/commit/?id=80323599e33f9c19287a1a3707481fb157b27052
git remote add broonie-spi https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
git fetch --no-tags broonie-spi for-next
git checkout 80323599e33f9c19287a1a3707481fb157b27052
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 <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202302121840.GtduUT37-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: MAINTAINERS references a file that doesn't exist: Documentation/devicetree/bindings/spi/brcm,bcm63xx-hsspi-peripheral-props.yaml
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-02-12 10:20 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=202302121840.GtduUT37-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=william.zhang@broadcom.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).