From: Segher Boessenkool <segher@kernel.crashing.org>
To: Olaf Hering <olh@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev@ozlabs.org, Eric Biederman <ebiederm@xmission.com>
Subject: Re: [PATCH] use correct register names in arch/ppc/kernel/relocate_kernel.S
Date: Wed, 29 Jun 2005 20:08:13 +0200 [thread overview]
Message-ID: <20750c905c7c0f2eccc3eba6dc1421db@kernel.crashing.org> (raw)
In-Reply-To: <20050629130113.GA30972@suse.de>
> --- linux-2.6.13-rc1.orig/arch/ppc/kernel/relocate_kernel.S
> +++ linux-2.6.13-rc1/arch/ppc/kernel/relocate_kernel.S
> @@ -34,9 +34,9 @@ relocate_new_kernel:
>
> mr r8, r0
> ori r8, r8, MSR_RI|MSR_ME
> - mtspr SRR1, r8
> + mtspr SPRN_SRR1, r8
> addi r8, r4, 1f - relocate_new_kernel
> - mtspr SRR0, r8
> + mtspr SPRN_SRR0, r8
> sync
> rfi
Or just mtsrr0 c.q. mtsrr1.
Segher
next prev parent reply other threads:[~2005-06-29 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 13:01 [PATCH] use correct register names in arch/ppc/kernel/relocate_kernel.S Olaf Hering
2005-06-29 18:08 ` Segher Boessenkool [this message]
2005-06-29 23:54 ` Benjamin Herrenschmidt
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=20750c905c7c0f2eccc3eba6dc1421db@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olh@suse.de \
/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).