From a667f1eb71a77859af6cedaadfab528256a99ca7 Mon Sep 17 00:00:00 2001 From: Zenghui Yu Date: Mon, 15 Jun 2026 00:14:58 +0800 Subject: [PATCH] cxl: docs/linux/dax-driver - fix typos Fix two obvious typos in the "kmem conversion" section. Signed-off-by: Zenghui Yu Reviewed-by: Alison Schofield Reviewed-by: Dongliang Mu Acked-by: Randy Dunlap Link: https://patch.msgid.link/20260614161458.88942-1-zenghui.yu@linux.dev Signed-off-by: Dave Jiang --- Documentation/driver-api/cxl/linux/dax-driver.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/driver-api/cxl/linux/dax-driver.rst b/Documentation/driver-api/cxl/linux/dax-driver.rst index 10d953a2167b..72c85a0f8606 100644 --- a/Documentation/driver-api/cxl/linux/dax-driver.rst +++ b/Documentation/driver-api/cxl/linux/dax-driver.rst @@ -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.