diff options
authorBernhard Walle <bwalle@suse.de>2008-06-26 21:55:18 +0200
committerIngo Molnar <mingo@elte.hu>2008-07-08 13:16:18 +0200
commit068b453834c4baf4e878481a9bd5103d54f60710 (patch)
parent32105f7fd8faa7bc3d101dcc3eabc0ae1ac375a7 (diff)
x86: fix documentation bug about relocatability
This patch fixes a small bug in documentation: x86_64 also has now the ability to build a relocatable kernel. Signed-off-by: Bernhard Walle <bwalle@suse.de> Cc: vgoyal@redhat.com Cc: kexec@lists.infradead.org Signed-off-by: Ingo Molnar <mingo@elte.hu>
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
index b8e52c0355d3..9691c7f5166c 100644
--- a/Documentation/kdump/kdump.txt
+++ b/Documentation/kdump/kdump.txt
@@ -109,7 +109,7 @@ There are two possible methods of using Kdump.
2) Or use the system kernel binary itself as dump-capture kernel and there is
no need to build a separate dump-capture kernel. This is possible
only with the architecutres which support a relocatable kernel. As
- of today i386 and ia64 architectures support relocatable kernel.
+ of today, i386, x86_64 and ia64 architectures support relocatable kernel.
Building a relocatable kernel is advantageous from the point of view that
one does not have to build a second kernel for capturing the dump. But

Privacy Policy