From: Simon Horman <horms@verge.net.au>
To: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Laurent Dufour <ldufour@linux.vnet.ibm.com>,
Kexec-ml <kexec@lists.infradead.org>
Subject: Re: [PATCH] kexec/ppc64: Handle reserved memory ranges exported by OPAL firmware.
Date: Thu, 15 May 2014 13:54:40 +0900 [thread overview]
Message-ID: <20140515045440.GC778@verge.net.au> (raw)
In-Reply-To: <53704F48.1030903@linux.vnet.ibm.com>
On Mon, May 12, 2014 at 10:04:16AM +0530, Mahesh Jagannath Salgaonkar wrote:
> On 05/11/2014 05:21 AM, Simon Horman wrote:
> > On Sun, Feb 09, 2014 at 10:25:45PM +0530, Mahesh J Salgaonkar wrote:
> >> From: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
> >>
> >> OPAL based system exports reserved memory ranges through /proc/device-tree
> >> for the regions that are reserved by OPAL firmware. Traverse
> >> /proc/device-tree/reserved-ranges and add them to exclude_ranges[] and
> >> reserve them.
> >>
> >> Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
> >
> > I apologise that this seems to have slipped through the cracks.
> > Manesh, is this patch still needed?
>
> Yup. We need this also.
Thanks, I have applied this too.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2014-05-15 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 16:55 [PATCH] kexec/ppc64: Handle reserved memory ranges exported by OPAL firmware Mahesh J Salgaonkar
2014-05-10 23:51 ` Simon Horman
2014-05-12 4:34 ` Mahesh Jagannath Salgaonkar
2014-05-15 4:54 ` Simon Horman [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=20140515045440.GC778@verge.net.au \
--to=horms@verge.net.au \
--cc=benh@kernel.crashing.org \
--cc=kexec@lists.infradead.org \
--cc=ldufour@linux.vnet.ibm.com \
--cc=mahesh@linux.vnet.ibm.com \
/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