From: Michael Ellerman <michael@ellerman.id.au>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.org, Fastboot mailing list <fastboot@lists.osdl.org>
Subject: Re: [PATCH] kexec: remove memory reserve patching for powerpc device tree
Date: Thu, 21 Sep 2006 11:59:04 +1000 [thread overview]
Message-ID: <1158803944.7062.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20060921011031.4BFEA67BCE@ozlabs.org>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
On Thu, 2006-09-21 at 11:10 +1000, Michael Neuling wrote:
> This code no longer needed with Jimi's auto reserve of device tree blob
> kernel patch now in 2.6.18.
>
> This patch will break Linux if you're kexecing to a kernel which doesn't
> have this patch (ie. earlier than 2.6.17). Required kernel patch is
> this one:
> http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4d1f3f25d9c303d1ce63b42cc94c54ac0ab2e950
>
Although it'd be nice to get rid of that code, I'm not sure we want to
go breaking this. This will mean RHEL5 and SLES10 users can't use
upstream kexec-tools :/
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-09-21 1:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 1:10 [PATCH] kexec: remove memory reserve patching for powerpc device tree Michael Neuling
2006-09-21 1:59 ` Michael Ellerman [this message]
2006-09-21 2:51 ` [Fastboot] " Horms
2006-09-21 3:40 ` Michael Ellerman
2006-09-21 4:04 ` Michael Neuling
2006-09-21 13:55 ` Vivek Goyal
2006-09-21 14:18 ` Jon Loeliger
2006-09-21 14:32 ` Vivek Goyal
2006-09-22 1:11 ` Michael Neuling
2006-09-22 1:21 ` Horms
2006-09-22 14:23 ` Vivek Goyal
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=1158803944.7062.9.camel@localhost.localdomain \
--to=michael@ellerman.id.au \
--cc=fastboot@lists.osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.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;
as well as URLs for NNTP newsgroup(s).