linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoffer Dall <cdall@cs.columbia.edu>,
	Raghavendra Rao Ananta <rananta@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-arm tree
Date: Wed, 04 May 2022 13:18:07 +0100	[thread overview]
Message-ID: <875yml8pa8.wl-maz@kernel.org> (raw)
In-Reply-To: <20220504205627.18f46380@canb.auug.org.au>

On Wed, 04 May 2022 11:56:27 +0100,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Hi all,
> 
> After merging the kvm-arm tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> Documentation/virt/kvm/arm/index.rst:7: WARNING: toctree contains reference to nonexisting document 'virt/kvm/arm/psci'
> Documentation/virt/kvm/arm/hypercalls.rst: WARNING: document isn't included in any toctree
> 
> Introduced by commit
> 
>   f1ced23a9be5 ("Docs: KVM: Rename psci.rst to hypercalls.rst")
> 

Thanks for the heads up, I have now pushed out a fix.

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2022-05-04 12:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 10:56 linux-next: build warning after merge of the kvm-arm tree Stephen Rothwell
2022-05-04 12:18 ` Marc Zyngier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-08 11:44 Stephen Rothwell
2021-04-08 14:35 ` Marc Zyngier
2020-10-02  8:41 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=875yml8pa8.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=cdall@cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rananta@google.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).