diff mbox series

daxctl: Fix kernel option typo in "Soft Reservation" theory of operation

Message ID 20220410123205.6045-2-msuchanek@suse.de (mailing list archive)
State Accepted
Commit 4bd100a8c97cfd9592be74af2e4699a2ab6d2f34
Headers show
Series daxctl: Fix kernel option typo in "Soft Reservation" theory of operation | expand

Commit Message

Michal Suchanek April 10, 2022, 12:32 p.m. UTC 
Fixes: 8f4e42c ("daxctl: Add "Soft Reservation" theory of operation")
Signed-off-by: Michal Suchanek <msuchanek@suse.de>
---
 Documentation/daxctl/daxctl-reconfigure-device.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff mbox series

Patch

diff --git a/Documentation/daxctl/daxctl-reconfigure-device.txt b/Documentation/daxctl/daxctl-reconfigure-device.txt
index 385c0c5..09691d2 100644
--- a/Documentation/daxctl/daxctl-reconfigure-device.txt
+++ b/Documentation/daxctl/daxctl-reconfigure-device.txt
@@ -91,8 +91,8 @@  details.
 Outside of the NUMA performance details linked above the other method to
 detect the presence of "Soft Reserved" memory is to dump /proc/iomem and
 look for "Soft Reserved" ranges. If the kernel was not built with
-CONFIG_EFI_SOFTRESERVE, predates the introduction of
-CONFIG_EFI_SOFTRESERVE (v5.5), or was booted with the efi=nosoftreserve
+CONFIG_EFI_SOFT_RESERVE, predates the introduction of
+CONFIG_EFI_SOFT_RESERVE (v5.5), or was booted with the efi=nosoftreserve
 command line then device-dax will not attach and the expectation is that
 the memory shows up as a memory-only NUMA node. Otherwise the memory
 shows up as a device-dax instance and DAXCTL(1) can be used to