All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Amit Machhiwal <amachhiw@linux.ibm.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>,
	linux-doc@vger.kernel.org
Subject: htmldocs: Documentation/virt/kvm/api.rst:6589: WARNING: Literal block expected; none found. [docutils]
Date: Thu, 14 May 2026 07:11:49 +0200	[thread overview]
Message-ID: <202605140717.W1StD3Ke-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/Amit-Machhiwal/KVM-PPC-Book3S-HV-Validate-arch_compat-against-host-compatibility-mode/20260514-003250
head:   14b4e064019c3de50b10ce42416ad214e65ab27d
commit: 14b4e064019c3de50b10ce42416ad214e65ab27d KVM: PPC: Document KVM_PPC_GET_COMPAT_CAPS ioctl
date:   12 hours ago
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux)
reproduce: (https://download.01.org/0day-ci/archive/20260514/202605140717.W1StD3Ke-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/202605140717.W1StD3Ke-lkp@intel.com/

All warnings (new ones prefixed by >>):

   Documentation/userspace-api/landlock:550: ./include/uapi/linux/landlock.h:45: ERROR: Unknown target name: "network flags". [docutils]
   Documentation/userspace-api/landlock:550: ./include/uapi/linux/landlock.h:50: ERROR: Unknown target name: "scope flags". [docutils]
   Documentation/userspace-api/landlock:550: ./include/uapi/linux/landlock.h:24: ERROR: Unknown target name: "filesystem flags". [docutils]
   Documentation/userspace-api/landlock:559: ./include/uapi/linux/landlock.h:168: ERROR: Unknown target name: "filesystem flags". [docutils]
   Documentation/userspace-api/landlock:559: ./include/uapi/linux/landlock.h:191: ERROR: Unknown target name: "network flags". [docutils]
>> Documentation/virt/kvm/api.rst:6589: WARNING: Literal block expected; none found. [docutils]
   Documentation/networking/skbuff:36: ./include/linux/skbuff.h:181: WARNING: Failed to create a cross reference. A title or caption not found: 'crc' [ref.ref]


vim +6589 Documentation/virt/kvm/api.rst

  6588	
> 6589	H_GUEST_CAP_POWER9  (bit 1): KVM guests can run in Power9 processor mode
  6590	H_GUEST_CAP_POWER10 (bit 2): KVM guests can run in Power10 processor mode
  6591	H_GUEST_CAP_POWER11 (bit 3): KVM guests can run in Power11 processor mode
  6592	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-05-14  5:11 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=202605140717.W1StD3Ke-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=amachhiw@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.