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 <[email protected]> --- 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
