Skip to contentSkip to conversation

cxl: docs/linux/dax-driver - fix typos

PATCH Applied Zenghui Yu 5 participants 5 messages Jun 14 – Jun 29

Subsystems (2)
lore
Share & tools
lore

Zenghui Yu

author
#0 lore raw

PATCH 1/1 cxl: docs/linux/dax-driver - fix typos

Fix two obvious typos in the "kmem conversion" section.

---
 Documentation/driver-api/cxl/linux/dax-driver.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/driver-api/cxl/linux/dax-driver.rst +2 -2
index 10d953a2167b..72c85a0f8606 100644
@@ -35,9 +35,9 @@ will be exposed to the kernel page allocator in the user-selected memory
 zone.
 
 The :code:`memmap_on_memory` setting (both global and DAX device local)
-dictates where the kernell will allocate the :code:`struct folio` descriptors
+dictates where the kernel will allocate the :code:`struct folio` descriptors
 for this memory will come from.  If :code:`memmap_on_memory` is set, memory
 hotplug will set aside a portion of the memory block capacity to allocate
 folios. If unset, the memory is allocated via a normal :code:`GFP_KERNEL`
-allocation - and as a result will most likely land on the local NUM node of the
+allocation - and as a result will most likely land on the local NUMA node of the
 CPU executing the hotplug operation.
Signature · 1 line
2.53.0
reviewer Acked-by on v1 1/1
#1 lore raw
Quoted 3 lines · Zenghui Yu

Fix two obvious typos in the "kmem conversion" section.

Thanks.

Quoted 20 lines
---
 Documentation/driver-api/cxl/linux/dax-driver.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/driver-api/cxl/linux/dax-driver.rst +2 -2
index 10d953a2167b..72c85a0f8606 100644
@@ -35,9 +35,9 @@ will be exposed to the kernel page allocator in the user-selected memory
 zone.
 
 The :code:`memmap_on_memory` setting (both global and DAX device local)
-dictates where the kernell will allocate the :code:`struct folio` descriptors
+dictates where the kernel will allocate the :code:`struct folio` descriptors
 for this memory will come from.  If :code:`memmap_on_memory` is set, memory
 hotplug will set aside a portion of the memory block capacity to allocate
 folios. If unset, the memory is allocated via a normal :code:`GFP_KERNEL`
-allocation - and as a result will most likely land on the local NUM node of the
+allocation - and as a result will most likely land on the local NUMA node of the
 CPU executing the hotplug operation.
Signature · 1 line
~Randy
Reviewed-by on v1 1/1
#2 lore raw
In reply to Zenghui Yu
Quoted 3 lines · Zenghui Yu

Fix two obvious typos in the "kmem conversion" section.

Quoted 20 lines
---
  Documentation/driver-api/cxl/linux/dax-driver.rst | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/driver-api/cxl/linux/dax-driver.rst +2 -2
index 10d953a2167b..72c85a0f8606 100644
@@ -35,9 +35,9 @@ will be exposed to the kernel page allocator in the user-selected memory
  zone.
 
  The :code:`memmap_on_memory` setting (both global and DAX device local)
-dictates where the kernell will allocate the :code:`struct folio` descriptors
+dictates where the kernel will allocate the :code:`struct folio` descriptors
  for this memory will come from.  If :code:`memmap_on_memory` is set, memory
  hotplug will set aside a portion of the memory block capacity to allocate
  folios. If unset, the memory is allocated via a normal :code:`GFP_KERNEL`
-allocation - and as a result will most likely land on the local NUM node of the
+allocation - and as a result will most likely land on the local NUMA node of the
  CPU executing the hotplug operation.
maintainer Applied
#4 lore raw
In reply to Zenghui Yu
Quoted 3 lines · Zenghui Yu

Fix two obvious typos in the "kmem conversion" section.

Applied to cxl/next
a667f1eb71a7

Quoted 20 lines
---
 Documentation/driver-api/cxl/linux/dax-driver.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/driver-api/cxl/linux/dax-driver.rst +2 -2
index 10d953a2167b..72c85a0f8606 100644
@@ -35,9 +35,9 @@ will be exposed to the kernel page allocator in the user-selected memory
 zone.
 
 The :code:`memmap_on_memory` setting (both global and DAX device local)
-dictates where the kernell will allocate the :code:`struct folio` descriptors
+dictates where the kernel will allocate the :code:`struct folio` descriptors
 for this memory will come from.  If :code:`memmap_on_memory` is set, memory
 hotplug will set aside a portion of the memory block capacity to allocate
 folios. If unset, the memory is allocated via a normal :code:`GFP_KERNEL`
-allocation - and as a result will most likely land on the local NUM node of the
+allocation - and as a result will most likely land on the local NUMA node of the
 CPU executing the hotplug operation.