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 <[email protected]>
---
Documentation/kdump/kdump.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
index b8e52c0..9691c7f 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
--
1.5.6
On Thu, Jun 26, 2008 at 09:55:18PM +0200, Bernhard Walle wrote:
> 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 <[email protected]>
Acked-by: mon Horman <[email protected]>
> ---
> Documentation/kdump/kdump.txt | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
> index b8e52c0..9691c7f 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
> --
> 1.5.6
>
>
> _______________________________________________
> kexec mailing list
> [email protected]
> http://lists.infradead.org/mailman/listinfo/kexec
--
Horms
* Bernhard Walle <[email protected]> wrote:
> This patch fixes a small bug in documentation: x86_64 also has now the
> ability to build a relocatable kernel.
applied to tip/x86/crashdump - thanks Bernhard.
Ingo