All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the origin tree
Date: Fri, 19 Feb 2021 16:33:49 +0100	[thread overview]
Message-ID: <87pn0w3wde.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20210219080235.52c8c7f4@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi all,
>
> Building Linus' tree, today's linux-next build (htmldocs) produced
> these warnings:
>
> Documentation/virt/kvm/api.rst:4537: WARNING: Unexpected indentation.
> Documentation/virt/kvm/api.rst:4539: WARNING: Block quote ends without a blank line; unexpected unindent.
>
> Introduced by commit
>
>   c21d54f0307f ("KVM: x86: hyper-v: allow KVM_GET_SUPPORTED_HV_CPUID as a system ioctl")
>
> These have been around for some time.

I remember seeing a patch fixing these:
https://lore.kernel.org/kvm/20210104095938.24838-1-lukas.bulwahn@gmail.com/

Paolo, could you please queue it up? Thanks!

-- 
Vitaly


  reply	other threads:[~2021-02-19 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 21:02 linux-next: build warnings after merge of the origin tree Stephen Rothwell
2021-02-19 15:33 ` Vitaly Kuznetsov [this message]
2021-02-19 16:01   ` Paolo Bonzini
2021-02-23 21:56     ` Stephen Rothwell
2021-02-26  1:57       ` Stephen Rothwell
2022-06-20  8:02 Stephen Rothwell
2023-05-08  4:39 Stephen Rothwell
2023-05-08  6:31 ` Maher Sanalla

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=87pn0w3wde.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --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 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.