diff mbox series

memory-hotplug.rst: fix wrong /sys/device/ path

Message ID ZQz1NUATBMOb3RT+@fedora
State New
Headers
Series memory-hotplug.rst: fix wrong /sys/device/ path |

Commit Message

Wang Jinchao Sept. 22, 2023, 2 a.m. UTC 
  Actually, it should be /sys/devices/

Signed-off-by: Wang Jinchao <wangjinchao@xfusion.com>
---
 Documentation/admin-guide/mm/memory-hotplug.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

Comments

David Hildenbrand Sept. 22, 2023, 7:33 a.m. UTC | #1 
On 22.09.23 04:00, Wang Jinchao wrote:
> Actually, it should be /sys/devices/
> 
> Signed-off-by: Wang Jinchao <wangjinchao@xfusion.com>
> ---
>   Documentation/admin-guide/mm/memory-hotplug.rst | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/admin-guide/mm/memory-hotplug.rst b/Documentation/admin-guide/mm/memory-hotplug.rst
> index cfe034cf1e87..01595965734a 100644
> --- a/Documentation/admin-guide/mm/memory-hotplug.rst
> +++ b/Documentation/admin-guide/mm/memory-hotplug.rst
> @@ -250,15 +250,15 @@ Observing the State of Memory Blocks
>   The state (online/offline/going-offline) of a memory block can be observed
>   either via::
>   
> -	% cat /sys/device/system/memory/memoryXXX/state
> +	% cat /sys/devices/system/memory/memoryXXX/state
>   
>   Or alternatively (1/0) via::
>   
> -	% cat /sys/device/system/memory/memoryXXX/online
> +	% cat /sys/devices/system/memory/memoryXXX/online
>   
>   For an online memory block, the managing zone can be observed via::
>   
> -	% cat /sys/device/system/memory/memoryXXX/valid_zones
> +	% cat /sys/devices/system/memory/memoryXXX/valid_zones
>   
>   Configuring Memory Hot(Un)Plug
>   ==============================
> @@ -326,7 +326,7 @@ however, a memory block might span memory holes. A memory block spanning memory
>   holes cannot be offlined.
>   
>   For example, assume 1 GiB memory block size. A device for a memory starting at
> -0x100000000 is ``/sys/device/system/memory/memory4``::
> +0x100000000 is ``/sys/devices/system/memory/memory4``::
>   
>   	(0x100000000 / 1Gib = 4)
>   

Reviewed-by: David Hildenbrand <david@redhat.com>
Jonathan Corbet Sept. 22, 2023, 11:19 a.m. UTC | #2 
Wang Jinchao <wangjinchao@xfusion.com> writes:

> Actually, it should be /sys/devices/
>
> Signed-off-by: Wang Jinchao <wangjinchao@xfusion.com>
> ---
>  Documentation/admin-guide/mm/memory-hotplug.rst | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

Applied, thanks.

jon
diff mbox series

Patch

diff --git a/Documentation/admin-guide/mm/memory-hotplug.rst b/Documentation/admin-guide/mm/memory-hotplug.rst
index cfe034cf1e87..01595965734a 100644
--- a/Documentation/admin-guide/mm/memory-hotplug.rst
+++ b/Documentation/admin-guide/mm/memory-hotplug.rst
@@ -250,15 +250,15 @@  Observing the State of Memory Blocks
 The state (online/offline/going-offline) of a memory block can be observed
 either via::
 
-	% cat /sys/device/system/memory/memoryXXX/state
+	% cat /sys/devices/system/memory/memoryXXX/state
 
 Or alternatively (1/0) via::
 
-	% cat /sys/device/system/memory/memoryXXX/online
+	% cat /sys/devices/system/memory/memoryXXX/online
 
 For an online memory block, the managing zone can be observed via::
 
-	% cat /sys/device/system/memory/memoryXXX/valid_zones
+	% cat /sys/devices/system/memory/memoryXXX/valid_zones
 
 Configuring Memory Hot(Un)Plug
 ==============================
@@ -326,7 +326,7 @@  however, a memory block might span memory holes. A memory block spanning memory
 holes cannot be offlined.
 
 For example, assume 1 GiB memory block size. A device for a memory starting at
-0x100000000 is ``/sys/device/system/memory/memory4``::
+0x100000000 is ``/sys/devices/system/memory/memory4``::
 
 	(0x100000000 / 1Gib = 4)