All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Chenyi Qiang <chenyi.qiang@intel.com>
Subject: Re: linux-next: build warnings after merge of the origin tree
Date: Fri, 26 Feb 2021 12:57:00 +1100	[thread overview]
Message-ID: <20210226125700.211c9c9d@canb.auug.org.au> (raw)
In-Reply-To: <20210224085654.34e61ec7@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]

Hi all,

On Wed, 24 Feb 2021 08:56:54 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Fri, 19 Feb 2021 17:01:13 +0100 Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> > On 19/02/21 16:33, Vitaly Kuznetsov wrote:  
> > > Stephen Rothwell <sfr@canb.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:

So the above are now gone, thanks, but the below is still there (line
number changed to 5004).

> 
> 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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-02-26  1:58 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
2021-02-19 16:01   ` Paolo Bonzini
2021-02-23 21:56     ` Stephen Rothwell
2021-02-26  1:57       ` Stephen Rothwell [this message]
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=20210226125700.211c9c9d@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=chenyi.qiang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=vkuznets@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 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.