From: Pratyush Yadav <pratyush@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
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: Fri, 20 Mar 2026 10:20:15 +0000 [thread overview]
Message-ID: <2vxz5x6qby5c.fsf@kernel.org> (raw)
In-Reply-To: <20260317140828.f5edbc151f85ffb8751b0f2d@linux-foundation.org> (Andrew Morton's message of "Tue, 17 Mar 2026 14:08:28 -0700")
On Tue, Mar 17 2026, Andrew Morton wrote:
> On Tue, 17 Mar 2026 09:09:36 +0000 Pratyush Yadav <pratyush@kernel.org> wrote:
[...]
>> Sorry, my bad for causing the confusion. I thought the radix tree
>> patches ("kho: adopt radix tree for preserved memory tracking") already
>> landed in mainline, but I went and checked and it seems that they
>> haven't. They are still in mm-unstable. So we should just meld this
>> patch ("kho: fix child node parsing for debugfs in/sub_fdts") into
>> ("kho: adopt radix tree for preserved memory tracking").
>
> OK, that's how we presently have things:
>
> kho-adopt-radix-tree-for-preserved-memory-tracking.patch
> kho-adopt-radix-tree-for-preserved-memory-tracking-fix.patch <- "kho: fix child node..."
> kho-remove-finalize-state-and-clients.patch
LGTM. Thanks!
[...]
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-03-20 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 3:35 [PATCH] kho: fix child node parsing for debugfs in/sub_fdts ranxiaokai627
2026-03-09 8:10 ` Mike Rapoport
2026-03-13 10:02 ` Pratyush Yadav
2026-03-14 22:46 ` Andrew Morton
2026-03-17 9:09 ` Pratyush Yadav
2026-03-17 21:08 ` Andrew Morton
2026-03-20 10:20 ` Pratyush Yadav [this message]
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=2vxz5x6qby5c.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=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=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 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.