From: Segher Boessenkool <segher@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>, paulus@samba.org
Subject: Re: [PATCH] [POWERPC] iSeries: clean up lparmap mess
Date: Mon, 20 Aug 2007 23:43:05 +0200 [thread overview]
Message-ID: <b6a8df562f181284195a2fedfccd5dc5@kernel.crashing.org> (raw)
In-Reply-To: <20070820145836.3fd8af11.sfr@canb.auug.org.au>
> We need to have xLparMap in ead_64.S so that it is at a fixed address
+h
> (because the linker will not resolve (address & 0xffffffff) for us).
> But the assembler miscalculates the KERNEL_VSID() expressions. So put
> the confusing expressions into asm-offset.c.
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
Looks just fine. It puts some stuff into head that doesn't
really belong there, but it sort-of was there already anyway ;-)
Nice cleanup no matter what, great :-)
> Segher: this was plan C :-)
Your plan C, my plan F :-)
Segher
prev parent reply other threads:[~2007-08-20 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 4:58 [PATCH] [POWERPC] iSeries: clean up lparmap mess Stephen Rothwell
2007-08-20 21:43 ` Segher Boessenkool [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=b6a8df562f181284195a2fedfccd5dc5@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).