From: Segher Boessenkool <segher@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>, ppc64-dev <linuxppc64-dev@ozlabs.org>
Subject: Re: [PATCH 8/9] powerpc: make iSeries build
Date: Sun, 2 Oct 2005 03:06:04 +0200 [thread overview]
Message-ID: <27c25b49c3f8c5d3f563a0b9b39bda8c@kernel.crashing.org> (raw)
In-Reply-To: <20051001001005.348d7798.sfr@canb.auug.org.au>
> The merge of vmlinux.lds.S would be much cleaner if it is clear that
> putting the ..start/end symbols inside the section definitions is OK on
> ppc32.
It is okay, and putting those symbol definitions
outside the section definition (like the ppc32
linker script used to do) can be wrong even, for
example, when the output sections need extra
alignment.
Segher
next prev parent reply other threads:[~2005-10-02 1:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 13:36 [PATCH 0/9] more merge changes Stephen Rothwell
2005-09-30 13:44 ` [PATCH 1/9] ppc64 iseries: move some iSeries include files Stephen Rothwell
2005-09-30 13:49 ` [PATCH 2/9] powerpc: merge asm-offsets.c Stephen Rothwell
2005-09-30 13:52 ` [PATCH 3/9] powerpc: remove old vector.S files Stephen Rothwell
2005-09-30 13:55 ` [PATCH 4/9] powerpc: more cleanup of powerpc/kernel Stephen Rothwell
2005-09-30 13:56 ` [PATCH 5/9] powerpc: Move lparmap.c to powerpc/platforms Stephen Rothwell
2005-09-30 14:00 ` [PATCH 6/9] powerpc: merge idle_power4.S and fixup traps.c Stephen Rothwell
2005-09-30 20:52 ` Kumar Gala
2005-10-01 2:17 ` Stephen Rothwell
2005-10-01 3:28 ` Paul Mackerras
2005-10-01 11:37 ` [PATCH 6/9] powerpc: merge idle_power4.S and traps.c Stephen Rothwell
2005-10-01 12:30 ` Stephen Rothwell
2005-09-30 14:05 ` [PATCH 7/9] ppc64: simplify the build a little Stephen Rothwell
2005-10-01 11:40 ` Stephen Rothwell
2005-09-30 14:10 ` [PATCH 8/9] powerpc: make iSeries build Stephen Rothwell
2005-10-02 1:06 ` Segher Boessenkool [this message]
2005-09-30 14:14 ` [PATCH 9/9] powerpc: make iSeries boot Stephen Rothwell
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=27c25b49c3f8c5d3f563a0b9b39bda8c@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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).