mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Bernhard Walle <bwalle@suse.de>
Cc: kexec@lists.infradead.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, vgoyal@redhat.com
Subject: Re: [PATCH] x86: Fix documentation bug about relocatability
Date: Tue, 1 Jul 2008 21:40:16 +1000	[thread overview]
Message-ID: <20080701114015.GA11207@verge.net.au> (raw)
In-Reply-To: <1214510118-21405-1-git-send-email-bwalle@suse.de>

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@suse.de>

Acked-by: mon Horman <horms@verge.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@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec

-- 
Horms


  reply	other threads:[~2008-07-01 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 19:55 Bernhard Walle
2008-07-01 11:40 ` Simon Horman [this message]
2008-07-03 13:16 ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080701114015.GA11207@verge.net.au \
    --to=horms@verge.net.au \
    --cc=bwalle@suse.de \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®