[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080701114015.GA11207@verge.net.au>
Date: Tue, 1 Jul 2008 21:40:16 +1000
From: Simon Horman <horms@...ge.net.au>
To: Bernhard Walle <bwalle@...e.de>
Cc: kexec@...ts.infradead.org, x86@...nel.org,
linux-kernel@...r.kernel.org, vgoyal@...hat.com
Subject: Re: [PATCH] x86: Fix documentation bug about relocatability
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 <bwalle@...e.de>
Acked-by: mon Horman <horms@...ge.net.au>
> ---
> 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
> kexec@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
--
Horms
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists