mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH] kho: docs: fix scratch_phys debugfs cross-reference
@ 2026-09-09 10:30 Kamalesh Babulal
  2026-09-09 10:32 ` sashiko-bot
  2026-09-10  9:50 ` Mike Rapoport
  0 siblings, 2 replies; 3+ messages in thread
From: Kamalesh Babulal @ 2026-09-09 10:30 UTC (permalink / raw)
  To: Alexander Graf, Mike Rapoport, Pasha Tatashin, Pratyush Yadav
  Cc: linux-kernel, kexec, linux-mm, Kamalesh Babulal

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-09-10  9:50 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-09-09 10:30 [PATCH] kho: docs: fix scratch_phys debugfs cross-reference Kamalesh Babulal
2026-09-09 10:32 ` sashiko-bot
2026-09-10  9:50 ` Mike Rapoport

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®