The scratch_phys documentation incorrectly tells users to use it
together with scratch_phys. It should refer to scratch_len, which
provides the length of each scratch region.

Signed-off-by: Kamalesh Babulal <kamalesh.babulal@oracle.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 2c26e560bd78..3e3912eeb2e6 100644
--- a/Documentation/admin-guide/mm/kho.rst
+++ b/Documentation/admin-guide/mm/kho.rst
@@ -104,7 +104,7 @@ stabilized.
 
 ``/sys/kernel/debug/kho/out/scratch_phys``
     Physical locations of KHO scratch regions. Kexec user space tools
-    can use this file in conjunction to scratch_phys to determine where
+    can use this file in conjunction to scratch_len to determine where
     it should place its payload images.
 
 ``/sys/kernel/debug/kho/out/sub_fdts/``
-- 
2.52.0

On Wed, 09 Sep 2026 16:00:01 +0530, Kamalesh Babulal wrote:
> kho: docs: fix scratch_phys debugfs cross-reference

Applied to liveupdate-7.4 branch of liveupdate/linux.git tree, thanks!

[1/1] kho: docs: fix scratch_phys debugfs cross-reference
      commit: dc645f2db7539352404525dd1b80236520fb39eb

tree: https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux
branch: liveupdate-7.4

--
Sincerely yours,
Mike.

> The scratch_phys documentation incorrectly tells users to use it
> together with scratch_phys. It should refer to scratch_len, which
> provides the length of each scratch region.
> 
> Signed-off-by: Kamalesh Babulal <kamalesh.babulal@oracle.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260909103001.2423403-1-kamalesh.babulal@oracle.com?part=1