All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH] docs: remove ia64 from kexec_and_kdump.txt
Date: Fri, 6 Dec 2013 11:10:56 +0000	[thread overview]
Message-ID: <52A1B0C0.3070403@citrix.com> (raw)
In-Reply-To: <1386274886-13105-1-git-send-email-olaf@aepfle.de>

On 05/12/13 20:21, Olaf Hering wrote:
> Signed-off-by: Olaf Hering <olaf@aepfle.de>

Acked-by: David Vrabel <david.vrabel@citrix.com>

> --- a/docs/misc/kexec_and_kdump.txt
> +++ b/docs/misc/kexec_and_kdump.txt
> @@ -137,10 +137,9 @@ command line parameter to the Xen hypervisor. It has two forms:
>        e.g. crashkernel=128M@256M
>  
>     Regardless of which of the two forms of the crashkernel command line you
> -   use, the crash kernel region should appear in /proc/iomem on x86 or
> -   /proc/iomem_machine on ia64. If it doesn't then either the crashkernel
> -   parameter is missing, or for some reason the region couldn't be placed -
> -   for instance because it is too large.
> +   use, the crash kernel region should appear in /proc/iomem on x86. If it
> +   doesn't then either the crashkernel parameter is missing, or for some
> +   reason the region couldn't be placed - for instance because it is too large.

Not related to this patch really, but this section talking about
/proc/iomem is only true for classic kernels.  Upstream kernels don't
have this information in /proc/iomem and it must be obtained by the
appropriate libxc call.

David

      reply	other threads:[~2013-12-06 11:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 20:21 [PATCH] docs: remove ia64 from kexec_and_kdump.txt Olaf Hering
2013-12-06 11:10 ` David Vrabel [this message]

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=52A1B0C0.3070403@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.