cxl: docs/linux/dax-driver - fix typos
Subsystems (2)
PATCH 1/1 cxl: docs/linux/dax-driver - fix typos
Fix two obvious typos in the "kmem conversion" section.
Signed-off-by Zenghui Yu <[email protected]>
--- 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
@@ -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
Quoted 3 lines · Zenghui Yu
Fix two obvious typos in the "kmem conversion" section.
Signed-off-by Zenghui Yu <[email protected]>
Acked-by Randy Dunlap <[email protected]>
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@@ -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
Quoted 3 lines · Zenghui Yu
Fix two obvious typos in the "kmem conversion" section.
Signed-off-by Zenghui Yu <[email protected]>
Reviewed-by Dongliang Mu <[email protected]>
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@@ -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.
Quoted 3 lines · Zenghui Yu
Fix two obvious typos in the "kmem conversion" section.
Signed-off-by Zenghui Yu <[email protected]>
Thanks,
Reviewed-by Alison Schofield <[email protected]>
Quoted 3 lines · Zenghui Yu
Fix two obvious typos in the "kmem conversion" section.
Signed-off-by Zenghui Yu <[email protected]>
Applied to cxl/nexta667f1eb71a7
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@@ -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.