From: Long Wei <longwei27@huawei.com>
To: <rppt@kernel.org>, <pasha.tatashin@soleen.com>,
<pratyush@kernel.org>, <akpm@linux-foundation.org>
Cc: <graf@amazon.com>, <leitao@debian.org>, <corbet@lwn.net>,
<rdunlap@infradead.org>, <linux-mm@kvack.org>,
<kexec@lists.infradead.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <hewenliang4@huawei.com>,
Long Wei <longwei27@huawei.com>
Subject: [PATCH v2 2/2] docs: kho: drop kho/in/sub_fdts description
Date: Thu, 19 Nov 2026 14:38:00 +0800 [thread overview]
Message-ID: <20261119063800.698863-3-longwei27@huawei.com> (raw)
In-Reply-To: <20261119063800.698863-1-longwei27@huawei.com>
The incoming sub-blob debugfs directory is gone, so remove its description
from the KHO admin guide.
Signed-off-by: Long Wei <longwei27@huawei.com>
---
Documentation/admin-guide/mm/kho.rst | 4 ----
1 file changed, 4 deletions(-)
diff --git a/Documentation/admin-guide/mm/kho.rst b/Documentation/admin-guide/mm/kho.rst
index 902d171a780a..4281da6be5fa 100644
--- a/Documentation/admin-guide/mm/kho.rst
+++ b/Documentation/admin-guide/mm/kho.rst
@@ -117,7 +117,3 @@ stabilized.
kernel's state is in this file in the format of flattened
device tree. This file may disappear when all consumers of
it finished to interpret their metadata.
-
-``/sys/kernel/debug/kho/in/sub_fdts/``
- Similar to ``kho/out/sub_fdts/``, but contains sub blobs
- of KHO producers passed from the old kernel.
--
2.43.0
next prev parent reply other threads:[~2026-11-19 6:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 9:29 [PATCH 0/2] kho: expose incoming sub-blob metadata instead of contents Long Wei
2026-11-17 9:29 ` [PATCH 1/2] " Long Wei
2026-11-18 16:38 ` Pasha Tatashin
2026-11-17 9:29 ` [PATCH 2/2] docs: kho: describe the in/blobs debugfs file Long Wei
2026-11-19 6:37 ` [PATCH v2 0/2] kho: drop the incoming sub-blob debugfs view Long Wei
2026-11-19 6:37 ` [PATCH v2 1/2] kho: do not expose incoming sub-blob contents in debugfs Long Wei
2026-11-19 8:26 ` Mike Rapoport
2026-11-19 6:38 ` Long Wei [this message]
2026-11-19 6:53 ` [PATCH v2 0/2] kho: drop the incoming sub-blob debugfs view Pasha Tatashin
2026-11-19 8:26 ` Mike Rapoport
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=20261119063800.698863-3-longwei27@huawei.com \
--to=longwei27@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=graf@amazon.com \
--cc=hewenliang4@huawei.com \
--cc=kexec@lists.infradead.org \
--cc=leitao@debian.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rdunlap@infradead.org \
--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®