kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
	Ben Gardon <bgardon@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the kvm tree
Date: Mon, 27 Jun 2022 16:57:34 +0700	[thread overview]
Message-ID: <Yrl/Dhm2zbK5mF4o@debian.me> (raw)
In-Reply-To: <20220627181937.3be67263@canb.auug.org.au>

On Mon, Jun 27, 2022 at 06:19:37PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the kvm tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> Documentation/virt/kvm/api.rst:8210: WARNING: Title underline too short.
> 
> 8.38 KVM_CAP_VM_DISABLE_NX_HUGE_PAGES
> ---------------------------
> Documentation/virt/kvm/api.rst:8217: WARNING: Unexpected indentation.
> 
> Introduced by commit
> 
>   084cc29f8bbb ("KVM: x86/MMU: Allow NX huge pages to be disabled on a per-vm basis")
> 

Hi Stephen and Paolo,

I have sent the fixes at [1], please test.

[1] https://lore.kernel.org/linux-doc/20220627095151.19339-1-bagasdotme@gmail.com/

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2022-06-27  9:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  8:19 linux-next: build warning after merge of the kvm tree Stephen Rothwell
2022-06-27  9:57 ` Bagas Sanjaya [this message]
2022-08-09  6:41 ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-11-14  3:13 Stephen Rothwell
2023-11-14 12:50 ` Paolo Bonzini
2022-12-13  4:41 Stephen Rothwell
2022-12-13  5:11 ` Sean Christopherson
2022-01-10  8:58 Stephen Rothwell
2022-01-11  2:55 ` Wang, Wei W
2022-01-20  3:36   ` Stephen Rothwell
2022-01-20  5:52     ` Wang, Wei W
2021-04-22  8:53 Stephen Rothwell
2021-02-09  9:59 Stephen Rothwell
2021-02-09 10:01 ` Paolo Bonzini
2019-11-25  3:03 Stephen Rothwell

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=Yrl/Dhm2zbK5mF4o@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=bgardon@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).