From: Johannes Weiner <hannes@cmpxchg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the mm tree
Date: Wed, 11 May 2022 12:06:09 -0400 [thread overview]
Message-ID: <Ynve8dg4zJyhH2gW@cmpxchg.org> (raw)
In-Reply-To: <20220511202045.45d84077@canb.auug.org.au>
On Wed, May 11, 2022 at 08:20:45PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mm tree, today's linux-next build (htmldocs) produced
> these warnings:
>
> Documentation/filesystems/proc.rst:1155: WARNING: Definition list ends without a blank line; unexpected unindent.
> Documentation/filesystems/proc.rst:1161: WARNING: Unexpected indentation.
> Documentation/filesystems/proc.rst:1162: WARNING: Block quote ends without a blank line; unexpected unindent.
> Documentation/filesystems/proc.rst:1165: WARNING: Unexpected indentation.
>
> Introduced by commit
>
> 9e43c820f7b2 ("Documentation: filesystems: proc: update meminfo section")
The patch below fixes it. The html output looks good too.
Andrew, could you please pick this up as delta for ^^^ ? Thanks!
Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
---
diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
index 736ed384750c..9749ff8c0ecf 100644
--- a/Documentation/filesystems/proc.rst
+++ b/Documentation/filesystems/proc.rst
@@ -1146,16 +1146,9 @@ CmaTotal
Memory reserved for the Contiguous Memory Allocator (CMA)
CmaFree
Free remaining memory in the CMA reserves
-HugePages_Total
-HugePages_Free
-HugePages_Rsvd
-HugePages_Surp
-Hugepagesize
-Hugetlb
+HugePages_Total, HugePages_Free, HugePages_Rsvd, HugePages_Surp, Hugepagesize, Hugetlb
See Documentation/admin-guide/mm/hugetlbpage.rst.
-DirectMap4k
-DirectMap2M
-DirectMap1G
+DirectMap4k, DirectMap2M, DirectMap1G
Breakdown of page table sizes used in the kernel's
identity mapping of RAM
next prev parent reply other threads:[~2022-05-11 16:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 10:20 linux-next: build warnings after merge of the mm tree Stephen Rothwell
2022-05-11 16:06 ` Johannes Weiner [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-23 3:54 Stephen Rothwell
2022-08-23 14:55 ` Liam Howlett
2022-11-22 6:50 Stephen Rothwell
2023-05-08 4:54 Stephen Rothwell
2023-05-08 16:10 ` Liam R. Howlett
2023-07-27 4:28 Stephen Rothwell
2023-07-27 4:46 ` Aneesh Kumar K.V
2023-07-27 5:00 ` Stephen Rothwell
2024-02-21 5:27 Stephen Rothwell
2024-02-21 17:12 ` SeongJae Park
2024-03-25 1:36 Stephen Rothwell
2024-03-26 2:19 ` Suren Baghdasaryan
2024-03-26 5:44 ` Randy Dunlap
2024-03-26 6:16 ` Suren Baghdasaryan
2024-03-28 4:39 ` Stephen Rothwell
2024-03-28 4:44 ` Stephen Rothwell
2024-03-28 5:35 ` Suren Baghdasaryan
2024-03-29 22:49 ` Stephen Rothwell
2024-03-29 23:01 ` Suren Baghdasaryan
2024-03-29 23:01 ` Suren Baghdasaryan
2024-07-01 1:01 Stephen Rothwell
2024-07-01 1:13 ` Andrii Nakryiko
2024-07-01 8:28 ` Stephen Rothwell
2024-07-01 8:49 Stephen Rothwell
2024-07-02 3:14 ` Andrew Morton
2024-07-02 4:15 ` Jiaqi Yan
2024-07-02 4:33 ` Jiaqi Yan
2024-07-02 6:18 ` Andrew Morton
2024-07-02 6:37 ` Jiaqi Yan
2024-07-02 23:09 ` SeongJae Park
2024-07-02 23:55 ` Jiaqi Yan
2024-09-11 10:21 Stephen Rothwell
2025-01-06 6:42 Stephen Rothwell
2025-02-09 23:06 Stephen Rothwell
2025-02-10 3:49 Stephen Rothwell
2025-02-17 6:10 Stephen Rothwell
2025-02-17 16:28 ` Suren Baghdasaryan
2025-03-05 9:42 Stephen Rothwell
2025-03-05 9:53 ` David Hildenbrand
2025-03-05 10:05 ` David Hildenbrand
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=Ynve8dg4zJyhH2gW@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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