From: Bagas Sanjaya <bagasdotme@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Ben Gardon <bgardon@google.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Paolo Bonzini <pbonzini@redhat.com>,
David Matlack <dmatlack@google.com>, Peter Xu <peterx@redhat.com>,
linux-doc@vger.kernel.org
Subject: Re: [linux-next:master 4541/7282] htmldocs: Documentation/virt/kvm/api.rst:8217: WARNING: Unexpected indentation.
Date: Sat, 2 Jul 2022 14:40:00 +0700 [thread overview]
Message-ID: <Yr/2UKna9f9b2O/D@debian.me> (raw)
In-Reply-To: <202207021352.PpKTUY8V-lkp@intel.com>
On Sat, Jul 02, 2022 at 01:07:39PM +0800, kernel test robot wrote:
> 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:8217: WARNING: Unexpected indentation.
>
> vim +8217 Documentation/virt/kvm/api.rst
>
> 8211
> 8212 :Capability KVM_CAP_VM_DISABLE_NX_HUGE_PAGES
> 8213 :Architectures: x86
> 8214 :Type: vm
> 8215 :Parameters: arg[0] must be 0.
> 8216 :Returns 0 on success, -EPERM if the userspace process does not
> > 8217 have CAP_SYS_BOOT, -EINVAL if args[0] is not 0 or any vCPUs have been
> 8218 created.
> 8219
>
I think this is fixed by this series [1].
[1]: https://lore.kernel.org/linux-doc/20220627095151.19339-1-bagasdotme@gmail.com/
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2022-07-02 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 5:07 kernel test robot
2022-07-02 7:40 ` Bagas Sanjaya [this message]
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=Yr/2UKna9f9b2O/D@debian.me \
--to=bagasdotme@gmail.com \
--cc=bgardon@google.com \
--cc=dmatlack@google.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.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