[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210224085654.34e61ec7@canb.auug.org.au>
Date: Wed, 24 Feb 2021 08:56:54 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Vitaly Kuznetsov <vkuznets@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Chenyi Qiang <chenyi.qiang@...el.com>
Subject: Re: linux-next: build warnings after merge of the origin tree
Hi all,
On Fri, 19 Feb 2021 17:01:13 +0100 Paolo Bonzini <pbonzini@...hat.com> wrote:
>
> On 19/02/21 16:33, Vitaly Kuznetsov wrote:
> > Stephen Rothwell <sfr@...b.auug.org.au> writes:
> >>
> >> 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!
>
> I was expecting Jon to pick it up, but yes I can do that too.
I am still seeing the above and have noticed another one:
Documentation/virt/kvm/api.rst:5002: WARNING: Unexpected indentation.
Documentation/virt/kvm/api.rst:5002: WARNING: Inline emphasis start-string without end-string.
Introduced by commit
c32b1b896d2a ("KVM: X86: Add the Document for KVM_CAP_X86_BUS_LOCK_EXIT")
(Not new, but newly reported - or maybe just changed line number)
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists