From: "longwei (I)" <longwei27@huawei.com>
To: Alexander Graf <graf@amazon.com>, Mike Rapoport <rppt@kernel.org>,
Changyuan Lyu <changyuanl@google.com>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: "hewenliang (C)" <hewenliang4@huawei.com>
Subject: [PATCH] kho: debugfs: Fix finalize interface documentation
Date: Fri, 17 Oct 2025 18:21:49 +0800 [thread overview]
Message-ID: <fe693f4d-80c7-4d1f-9430-3ab9c8165df0@huawei.com> (raw)
From 91c2b24855d55fef0e8919b2d39216d5c9aad558 Mon Sep 17 00:00:00 2001
From: Long Wei <longwei27@huawei.com>
Date: Wed, 15 Oct 2025 19:58:39 +0800
Subject: [PATCH]kho: debugfs: Fix finalize interface documentation
Correct the error in the KHO documentation:
when removing the KHO finalization phase, it is necessary
to execute echo 0 > /sys/kernel/debug/kho/out/finalize
instead of echo 0 > /sys/kernel/debug/kho/out/active.
Fix it.
Signed-off-by: Long Wei <longwei27@huawei.com>
---
Documentation/admin-guide/mm/kho.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/mm/kho.rst b/Documentation/admin-guide/mm/kho.rst
index 6dc18ed4b..2eda33865 100644
--- a/Documentation/admin-guide/mm/kho.rst
+++ b/Documentation/admin-guide/mm/kho.rst
@@ -57,7 +57,7 @@ Abort a KHO exec
You can move the system out of KHO finalization phase again by calling ::
- $ echo 0 > /sys/kernel/debug/kho/out/active
+ $ echo 0 > /sys/kernel/debug/kho/out/finalize
After this command, the KHO FDT is no longer available in
``/sys/kernel/debug/kho/out/fdt``.
--
2.43.0
next reply other threads:[~2025-10-17 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 10:21 longwei (I) [this message]
2025-10-19 14:39 ` Mike Rapoport
2025-10-22 11:21 ` 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=fe693f4d-80c7-4d1f-9430-3ab9c8165df0@huawei.com \
--to=longwei27@huawei.com \
--cc=changyuanl@google.com \
--cc=graf@amazon.com \
--cc=hewenliang4@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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®