From: Kumar Gala <galak@kernel.crashing.org>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: linuxppc-dev@ozlabs.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH 2/3] powerpc/fsl head: move the entry setup code into a seperate file
Date: Mon, 24 May 2010 14:01:48 -0500 [thread overview]
Message-ID: <2E25F460-0EA6-4035-8A38-96D42CC9CD24@kernel.crashing.org> (raw)
In-Reply-To: <1270412343-19334-3-git-send-email-sebastian@breakpoint.cc>
On Apr 4, 2010, at 3:19 PM, Sebastian Andrzej Siewior wrote:
> From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>=20
> This patch only moves the initial entry code which setups the mapping
> from what ever to KERNELBASE into a seperate file. No code change has
> been made here.
>=20
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> arch/powerpc/kernel/fsl_booke_entry_mapping.S | 200 =
+++++++++++++++++++++++++
> arch/powerpc/kernel/head_fsl_booke.S | 199 =
+------------------------
> 2 files changed, 201 insertions(+), 198 deletions(-)
> create mode 100644 arch/powerpc/kernel/fsl_booke_entry_mapping.S
applied to next
- k=
next prev parent reply other threads:[~2010-05-24 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 20:19 Kexec on FSL-Book-E, v4 Sebastian Andrzej Siewior
2010-04-04 20:19 ` [PATCH 1/3] powerpc/head fsl: fix the case where we are not in the first page Sebastian Andrzej Siewior
2010-05-24 19:01 ` Kumar Gala
2010-04-04 20:19 ` [PATCH 2/3] powerpc/fsl head: move the entry setup code into a seperate file Sebastian Andrzej Siewior
2010-05-24 19:01 ` Kumar Gala [this message]
2010-04-04 20:19 ` [PATCH 3/3] powerpc/kexec: Add support for FSL-BookE Sebastian Andrzej Siewior
2010-05-07 6:50 ` Kumar Gala
2010-05-07 7:24 ` Sebastian Andrzej Siewior
2010-05-07 11:35 ` wilbur.chan
2010-05-07 12:16 ` Josh Boyer
2010-05-07 12:50 ` Kumar Gala
2010-05-24 19:01 ` Kumar Gala
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=2E25F460-0EA6-4035-8A38-96D42CC9CD24@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=bigeasy@linutronix.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=sebastian@breakpoint.cc \
/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).