From: kernel test robot <lkp@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org
Subject: [jgunthorpe:pcie_switch_groups 5/12] htmldocs: Documentation/driver-api/pci/pci:19: ./drivers/pci/search.c:611: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Date: Sat, 6 Sep 2025 10:32:59 +0200 [thread overview]
Message-ID: <202509061043.HTW4fby7-lkp@intel.com> (raw)
tree: https://github.com/jgunthorpe/linux pcie_switch_groups
head: b07d062a257fab9b08dc1b6708ada05aa90d4cf8
commit: c99c2800fa7ff067b894e473bf60473ca4b7ee4c [5/12] PCI: Add pci_reachable_set()
reproduce: (https://download.01.org/0day-ci/archive/20250906/202509061043.HTW4fby7-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/202509061043.HTW4fby7-lkp@intel.com/
All warnings (new ones prefixed by >>):
WARNING: No kernel-doc for file ./include/linux/pwm.h
ERROR: Cannot find file ./include/linux/mtd/rawnand.h
ERROR: Cannot find file ./include/linux/mtd/rawnand.h
WARNING: No kernel-doc for file ./include/linux/mtd/rawnand.h
Documentation/driver-api/pci/pci:19: ./drivers/pci/search.c:610: ERROR: Unexpected indentation. [docutils]
>> Documentation/driver-api/pci/pci:19: ./drivers/pci/search.c:611: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
ERROR: Cannot find file ./include/linux/pm.h
WARNING: No kernel-doc for file ./include/linux/pm.h
ERROR: Cannot find file ./include/linux/pwrseq/provider.h
ERROR: Cannot find file ./include/linux/pwrseq/provider.h
WARNING: No kernel-doc for file ./include/linux/pwrseq/provider.h
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-09-06 8:33 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=202509061043.HTW4fby7-lkp@intel.com \
--to=lkp@intel.com \
--cc=jgg@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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).