From: Simon Horman <horms@verge.net.au>
To: Alan Modra <amodra@gmail.com>
Cc: Milton Miller <miltonm@bga.com>,
Michael Neuling <mikey@neuling.org>,
kexec@lists.infradead.org, Anton Blanchard <anton@samba.org>,
Matt Evans <matt@ozlabs.org>
Subject: Re: [PATCH 1/3] kexec-tools: powerpc: Fix 64bit optimize for size (gcc -Os) build
Date: Fri, 18 Nov 2011 08:48:29 +0900 [thread overview]
Message-ID: <20111117234829.GA14082@verge.net.au> (raw)
In-Reply-To: <20111114223036.GK14325@bubble.grove.modra.org>
On Tue, Nov 15, 2011 at 09:00:38AM +1030, Alan Modra wrote:
> On Tue, Nov 15, 2011 at 09:24:06AM +1100, Anton Blanchard wrote:
> > I wonder why we aren't building and linking an -fpic object, wouldn't
> > it make the relocation code much simpler?
>
> No, powerpc64 is PIC anyway.
Hi Alan, Hi Anton, Hi all,
I am wondering if you are comfortable with me (finally) releasing
a new version of kexec-tools with this series of patches applied.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-11-18 2:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 7:53 [PATCH 1/3] kexec-tools: powerpc: Fix 64bit optimize for size (gcc -Os) build Anton Blanchard
2011-11-14 7:54 ` [PATCH 2/3] kexec-tools: powerpc: Add more 64bit relocations Anton Blanchard
2011-11-14 7:56 ` [PATCH 3/3] kexec-tools: powerpc: Cleanup relocation code Anton Blanchard
2011-11-14 8:46 ` [PATCH 1/3] kexec-tools: powerpc: Fix 64bit optimize for size (gcc -Os) build Simon Horman
2011-11-14 22:14 ` Alan Modra
2011-11-14 22:24 ` Anton Blanchard
2011-11-14 22:30 ` Alan Modra
2011-11-17 23:48 ` Simon Horman [this message]
2011-11-28 11:49 ` Anton Blanchard
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=20111117234829.GA14082@verge.net.au \
--to=horms@verge.net.au \
--cc=amodra@gmail.com \
--cc=anton@samba.org \
--cc=kexec@lists.infradead.org \
--cc=matt@ozlabs.org \
--cc=mikey@neuling.org \
--cc=miltonm@bga.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