From 31cd140dd2efddebe4cff9c584f590840c2b15c1 Mon Sep 17 00:00:00 2001 From: Bernhard Walle Date: Thu, 26 Jun 2008 21:55:18 +0200 Subject: [PATCH] --- yaml --- r: 99991 b: refs/heads/master c: 068b453834c4baf4e878481a9bd5103d54f60710 h: refs/heads/master i: 99989: 0492120edb759289dec908668483314d159b6aa7 99987: 6299c7d84601e327dd8ad87af50b21a40ad7de3b 99983: a95a47aee195c313d406f56ae883dc747ccfc082 v: v3 --- [refs] | 2 +- trunk/Documentation/kdump/kdump.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index b65c877bdc1a..6f3d39d3ef25 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 32105f7fd8faa7bc3d101dcc3eabc0ae1ac375a7 +refs/heads/master: 068b453834c4baf4e878481a9bd5103d54f60710 diff --git a/trunk/Documentation/kdump/kdump.txt b/trunk/Documentation/kdump/kdump.txt index b8e52c0355d3..9691c7f5166c 100644 --- a/trunk/Documentation/kdump/kdump.txt +++ b/trunk/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