From: Baoquan He <bhe@redhat.com>
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 warning after merge of the mm-unstable tree
Date: Mon, 20 Oct 2025 11:41:50 +0800 [thread overview]
Message-ID: <aPWvfu5MQROcWKOf@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20251020134517.795a133d@canb.auug.org.au>
On 10/20/25 at 01:45pm, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mm-unstable tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Documentation/admin-guide/mm/index.rst:24: WARNING: toctree contains reference to nonexisting document 'admin-guide/mm/swap_numa' [toc.not_readable]
>
> Introduced by commit
>
> 9e1d0b5b7f28 ("mm/swap: do not choose swap device according to numa node")
Thanks, Stephen.
Below fix can be appended to commit 9e1d0b5b7f28 to fix the building
warning. Not sure if I need respin v5 to include this.
From 0c6f376f320dcc4d902377d540adc519394cdb12 Mon Sep 17 00:00:00 2001
From: Baoquan He <bhe@redhat.com>
Date: Mon, 20 Oct 2025 11:37:09 +0800
Subject: [PATCH] doc: clean up the relics of swap_numa
Content-type: text/plain
The doc swap_numa.rst has been removed in mm-new commit 9e1d0b5b7f28
("mm/swap: do not choose swap device according to numa node"). Clean up
the rest in mm/index.rst.
Signed-off-by: Baoquan He <bhe@redhat.com>
---
Documentation/admin-guide/mm/index.rst | 1 -
1 file changed, 1 deletion(-)
diff --git a/Documentation/admin-guide/mm/index.rst b/Documentation/admin-guide/mm/index.rst
index ebc83ca20fdc..bbb563cba5d2 100644
--- a/Documentation/admin-guide/mm/index.rst
+++ b/Documentation/admin-guide/mm/index.rst
@@ -39,7 +39,6 @@ the Linux memory management.
shrinker_debugfs
slab
soft-dirty
- swap_numa
transhuge
userfaultfd
zswap
--
2.41.0
next prev parent reply other threads:[~2025-10-20 3:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 2:45 linux-next: build warning after merge of the mm-unstable tree Stephen Rothwell
2025-10-20 3:41 ` Baoquan He [this message]
2025-10-20 4:19 ` Bagas Sanjaya
-- strict thread matches above, loose matches on Subject: below --
2025-11-07 3:39 Stephen Rothwell
2025-11-07 6:51 ` Randy Dunlap
2025-10-20 2:49 Stephen Rothwell
2025-09-12 4:12 Stephen Rothwell
2025-09-12 4:58 ` Balbir Singh
2025-09-04 2:14 Stephen Rothwell
2025-09-04 2:59 ` Andrew Morton
2025-09-04 6:33 ` David Hildenbrand
2025-07-15 8:55 Stephen Rothwell
2025-07-15 18:54 ` SeongJae Park
2025-07-10 7:54 Stephen Rothwell
2025-07-10 22:30 ` Andrew Morton
2025-07-10 22:49 ` Stephen Rothwell
2025-07-11 0:36 ` Randy Dunlap
2025-07-11 6:28 ` David Hildenbrand
2025-07-10 7:50 Stephen Rothwell
2025-07-11 9:57 ` David Hildenbrand
2025-06-10 4:33 Stephen Rothwell
2025-06-10 4:35 ` Christoph Hellwig
2025-05-09 9:43 Stephen Rothwell
2025-05-09 20:31 ` Andrew Morton
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=aPWvfu5MQROcWKOf@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--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 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.