From: kernel test robot <lkp@intel.com>
To: Yi Liu <yi.l.liu@intel.com>, Kevin Tian <kevin.tian@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [yiliu1765-iommufd:tmp/for-baol-0303 7/53] htmldocs: Documentation/virt/kvm/devices/vfio.rst:45: WARNING: Literal block expected; none found.
Date: Sat, 4 Mar 2023 20:40:46 +0800 [thread overview]
Message-ID: <202303042022.MPIugesS-lkp@intel.com> (raw)
tree: https://github.com/yiliu1765/iommufd.git tmp/for-baol-0303
head: 028abaf51f935755b020cbb2c8f196862dd3a312
commit: 29e1a8a95519040661aa3370fb58cd9ee8d6cb57 [7/53] docs: kvm: vfio: Require call KVM_DEV_VFIO_GROUP_ADD before VFIO_GROUP_GET_DEVICE_FD
reproduce:
# https://github.com/yiliu1765/iommufd/commit/29e1a8a95519040661aa3370fb58cd9ee8d6cb57
git remote add yiliu1765-iommufd https://github.com/yiliu1765/iommufd.git
git fetch --no-tags yiliu1765-iommufd tmp/for-baol-0303
git checkout 29e1a8a95519040661aa3370fb58cd9ee8d6cb57
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/202303042022.MPIugesS-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/virt/kvm/devices/vfio.rst:45: WARNING: Literal block expected; none found.
vim +45 Documentation/virt/kvm/devices/vfio.rst
44
> 45 The GROUP_ADD operation above should be invoked prior to accessing the
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-03-04 12:40 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=202303042022.MPIugesS-lkp@intel.com \
--to=lkp@intel.com \
--cc=kevin.tian@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yi.l.liu@intel.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 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.