From: Catalin Marinas <catalin.marinas@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Will Deacon <will@kernel.org>, Baoquan He <bhe@redhat.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 arm64 tree
Date: Tue, 13 Jun 2023 16:59:22 +0100 [thread overview]
Message-ID: <ZIiSWjO2GNouHBKe@arm.com> (raw)
In-Reply-To: <20230613162344.1dcb6ac0@canb.auug.org.au>
On Tue, Jun 13, 2023 at 04:23:44PM +1000, Stephen Rothwell wrote:
> After merging the arm64 tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/arm64/kdump.rst: WARNING: document isn't included in any toctree
>
> Introduced by commit
>
> 03dc0e05407f ("Documentation: add kdump.rst to present crashkernel reservation on arm64")
Thanks. I have a patch already from Baoquan, I'll push it later today.
--
Catalin
next prev parent reply other threads:[~2023-06-13 15:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 6:23 linux-next: build warning after merge of the arm64 tree Stephen Rothwell
2023-06-13 15:59 ` Catalin Marinas [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-24 6:24 Stephen Rothwell
2023-10-24 9:55 ` Catalin Marinas
2023-10-24 13:42 ` Ard Biesheuvel
2023-10-24 16:14 ` Catalin Marinas
2022-07-07 9:57 Stephen Rothwell
2022-07-07 10:28 ` Will Deacon
2022-03-09 11:34 Stephen Rothwell
2022-03-09 12:18 ` Will Deacon
2018-07-23 23:05 Stephen Rothwell
2018-07-24 0:26 ` AKASHI Takahiro
2018-07-24 8:12 ` Arnd Bergmann
2018-07-24 9:30 ` Ard Biesheuvel
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=ZIiSWjO2GNouHBKe@arm.com \
--to=catalin.marinas@arm.com \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=will@kernel.org \
/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.