From: Will Deacon <will@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Huang Shijie <shijie@os.amperecomputing.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: Wed, 9 Mar 2022 12:18:35 +0000 [thread overview]
Message-ID: <20220309121834.GC397@willie-the-truck> (raw)
In-Reply-To: <20220309223411.5492e665@canb.auug.org.au>
On Wed, Mar 09, 2022 at 10:34:11PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the arm64 tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/admin-guide/kdump/vmcoreinfo.rst:498: WARNING: Title underline too short.
>
> MODULES_VADDR|MODULES_END|VMALLOC_START|VMALLOC_END|VMEMMAP_START|VMEMMAP_END
> -------------
>
> Introduced by commit
>
> 2369f171d5c5 ("arm64: crash_core: Export MODULES, VMALLOC, and VMEMMAP ranges")
Cheers, I'll fix this.
Will
next prev parent reply other threads:[~2022-03-09 12:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 11:34 linux-next: build warning after merge of the arm64 tree Stephen Rothwell
2022-03-09 12:18 ` Will Deacon [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
2023-06-13 6:23 Stephen Rothwell
2023-06-13 15:59 ` Catalin Marinas
2022-07-07 9:57 Stephen Rothwell
2022-07-07 10:28 ` 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=20220309121834.GC397@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shijie@os.amperecomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox