[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190514161724.16604-1-cengizc@gmail.com>
Date: Tue, 14 May 2019 19:17:25 +0300
From: Cengiz Can <cengizc@...il.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Jonathan Corbet <corbet@....net>, kexec@...ts.infradead.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
cengizc@...il.com
Subject: [PATCH] Documentation: kdump: fix minor typo
kdump.txt had a minor typo.
Signed-off-by: Cengiz Can <cengizc@...il.com>
---
Documentation/kdump/kdump.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
index 51814450a7f8..3162eeb8c262 100644
--- a/Documentation/kdump/kdump.txt
+++ b/Documentation/kdump/kdump.txt
@@ -410,7 +410,7 @@ Notes on loading the dump-capture kernel:
* Boot parameter "1" boots the dump-capture kernel into single-user
mode without networking. If you want networking, use "3".
-* We generally don' have to bring up a SMP kernel just to capture the
+* We generally don't have to bring up a SMP kernel just to capture the
dump. Hence generally it is useful either to build a UP dump-capture
kernel or specify maxcpus=1 option while loading dump-capture kernel.
Note, though maxcpus always works, you had better replace it with
--
2.21.0
Powered by blists - more mailing lists