From: Andrew Morton <akpm@linux-foundation.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: ranxiaokai627@163.com, graf@amazon.com, rppt@kernel.org,
pasha.tatashin@soleen.com, jasonmiu@google.com,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
ran.xiaokai@zte.com.cn, Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH] kho: fix child node parsing for debugfs in/sub_fdts
Date: Sat, 14 Mar 2026 15:46:37 -0700 [thread overview]
Message-ID: <20260314154637.86a7d4f07800b59c00049814@linux-foundation.org> (raw)
In-Reply-To: <2vxzpl58f3oh.fsf@kernel.org>
On Fri, 13 Mar 2026 10:02:06 +0000 Pratyush Yadav <pratyush@kernel.org> wrote:
> On Mon, Mar 09 2026, ranxiaokai627@163.com wrote:
>
> > From: Ran Xiaokai <ran.xiaokai@zte.com.cn>
> >
> > Commit e0c1731f5d57 ("kho: adopt radix tree for preserved memory tracking")
> > changed KHO_FDT_SUB_TREE_PROP_NAME from "fdt" to "preserved-data". However,
> > kho debugfs code still hard-coded the "fdt" string when parsing the
> > device tree, causing the debugfs node /debugfs/kho/in/sub_fdts/
> > fail to parse child nodes correctly.
> >
> > Fix this by including the header file and using KHO_FDT_SUB_TREE_PROP_NAME
> > instead of the hard-coded string.
> >
> > Fixes: e0c1731f5d57 ("kho: adopt radix tree for preserved memory tracking")
> > Signed-off-by: Ran Xiaokai <ran.xiaokai@zte.com.cn>
>
> Breno's patch [0] also fixes this, but I'd rather have this go through
> hotfixes and get backported to stable, and Breno's series to build on
> top of this.
>
> [0] https://lore.kernel.org/linux-mm/20260309-kho-v8-4-c3abcf4ac750@debian.org/
Confused. This patch (kho: fix child node parsing for debugfs
in/sub_fdts) fixes the mm-unstable patch "kho: adopt radix tree for
preserved memory tracking".
So what are you suggesting be added to -stable?
(Please lay it all out very clearly, idenfifying patches by name!)
next prev parent reply other threads:[~2026-03-14 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 3:35 ranxiaokai627
2026-03-09 8:10 ` Mike Rapoport
2026-03-13 10:02 ` Pratyush Yadav
2026-03-14 22:46 ` Andrew Morton [this message]
2026-03-17 9:09 ` Pratyush Yadav
2026-03-17 21:08 ` Andrew Morton
2026-03-20 10:20 ` Pratyush Yadav
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=20260314154637.86a7d4f07800b59c00049814@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=graf@amazon.com \
--cc=jasonmiu@google.com \
--cc=kexec@lists.infradead.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=ran.xiaokai@zte.com.cn \
--cc=ranxiaokai627@163.com \
--cc=rppt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®