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 140/308] htmldocs: Documentation/virt/kvm/api.rst:1362: WARNING: Literal block ends without a blank line; unexpected unindent.
Date: Wed, 17 Aug 2022 11:21:23 +0800	[thread overview]
Message-ID: <202208171109.lCfseeP6-lkp@intel.com> (raw)

tree:   https://github.com/intel/tdx.git kvm-upstream-workaround
head:   85c097fdd1667a842a9e75d8f658fc16bd72981a
commit: bb90daae9d75517eb0fddd87e26149ed7612995a [140/308] 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:1362: WARNING: Literal block ends without a blank line; unexpected unindent.

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

  1347	
  1348	  struct kvm_userspace_memory_region {
  1349		__u32 slot;
  1350		__u32 flags;
  1351		__u64 guest_phys_addr;
  1352		__u64 memory_size; /* bytes */
  1353		__u64 userspace_addr; /* start of the userspace allocated memory */
  1354	  };
  1355	
  1356	  struct kvm_userspace_memory_region_ext {
  1357		struct kvm_userspace_memory_region region;
  1358		__u64 private_offset;
  1359		__u32 private_fd;
  1360		__u32 pad1;
  1361		__u64 pad2[14];
> 1362	};
  1363	
  1364	  /* for kvm_memory_region::flags */
  1365	  #define KVM_MEM_LOG_DIRTY_PAGES	(1UL << 0)
  1366	  #define KVM_MEM_READONLY	(1UL << 1)
  1367	  #define KVM_MEM_PRIVATE		(1UL << 2)
  1368	

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

                 reply	other threads:[~2022-08-17  3:22 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=202208171109.lCfseeP6-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®