From: Anton Blanchard <anton@samba.org>
To: "Moffett, Kyle D" <Kyle.D.Moffett@boeing.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Livingston, John A" <john.a.livingston@boeing.com>,
Matthew McClintock <msm@freescale.com>
Subject: Re: mpc85xx: kexec build broken by "powerpc/kexec: Remove ppc_md.machine_kexec"
Date: Thu, 24 Feb 2011 09:11:21 +1100 [thread overview]
Message-ID: <20110224091121.43b31dad@kryten> (raw)
In-Reply-To: <B87A2622-0006-4FC8-893A-41DBBF0CA170@boeing.com>
Hi Kyle,
> As far as I can tell, "machine_kexec" was removed in commit c9486878
> (powerpc/kexec: Remove ppc_md.machine_kexec) on Jan 6th, 2011, which
> claims that it was not used.
>
> Unfortunately it looks like it *is* used by the mpc85xx kexec()
> support (commit f933a41e), added on Jul 21, 2010.
Thanks for the report. Testing a patch now.
Anton
prev parent reply other threads:[~2011-02-23 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 20:54 mpc85xx: kexec build broken by "powerpc/kexec: Remove ppc_md.machine_kexec" Moffett, Kyle D
2011-02-23 22:11 ` Anton Blanchard [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=20110224091121.43b31dad@kryten \
--to=anton@samba.org \
--cc=Kyle.D.Moffett@boeing.com \
--cc=john.a.livingston@boeing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msm@freescale.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;
as well as URLs for NNTP newsgroup(s).