[intel-tdx:kvm-upstream-workaround 329/442] htmldocs: Documentation/virt/kvm/api.rst:1364: WARNING: Inline emphasis start-string without end-string.

mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed

From: kernel test robot <lkp@intel.com>
To: Chao Peng <chao.p.peng@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Isaku Yamahata <isaku.yamahata@intel.com>,
	Yu Zhang <yu.c.zhang@linux.intel.com>,
	linux-doc@vger.kernel.org
Subject: [intel-tdx:kvm-upstream-workaround 329/442] htmldocs: Documentation/virt/kvm/api.rst:1364: WARNING: Inline emphasis start-string without end-string.
Date: Wed, 6 Jul 2022 01:37:10 +0800	[thread overview]
Message-ID: <202207060157.oZAr0KUU-lkp@intel.com> (raw)

tree:   https://github.com/intel/tdx.git kvm-upstream-workaround
head:   8af973ebaf30642129fc1ca63f155a469f9615ed
commit: 088ff1f7cc255f6cef6bbe6bdeac7bef64d76ba5 [329/442] KVM: Extend the memslot to support fd-based private memory
reproduce: make htmldocs

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> Documentation/virt/kvm/api.rst:1364: WARNING: Inline emphasis start-string without end-string.

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

088ff1f7cc255f Documentation/virt/kvm/api.rst    Chao Peng      2021-11-15  1363  
0f2d8f4dd0663d Documentation/kvm/api.txt         Avi Kivity     2010-03-25 @1364    /* for kvm_memory_region::flags */
4d8b81abc47b83 Documentation/virtual/kvm/api.txt Xiao Guangrong 2012-08-21  1365    #define KVM_MEM_LOG_DIRTY_PAGES	(1UL << 0)
4d8b81abc47b83 Documentation/virtual/kvm/api.txt Xiao Guangrong 2012-08-21  1366    #define KVM_MEM_READONLY	(1UL << 1)
088ff1f7cc255f Documentation/virt/kvm/api.rst    Chao Peng      2021-11-15  1367    #define KVM_MEM_PRIVATE		(1UL << 2)
0f2d8f4dd0663d Documentation/kvm/api.txt         Avi Kivity     2010-03-25  1368  

:::::: The code at line 1364 was first introduced by commit
:::::: 0f2d8f4dd0663defff8c1738d33478c1fb65a4f5 KVM: Document KVM_SET_USER_MEMORY_REGION

:::::: TO: Avi Kivity <avi@redhat.com>
:::::: CC: Avi Kivity <avi@redhat.com>

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-07-05 17: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=202207060157.oZAr0KUU-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=isaku.yamahata@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yu.c.zhang@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®