From: Dimitry Andric <dimitry@andric.com>
To: saeed bishara <saeed.bishara@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
Paolo Ornati <ornati@fastwebnet.it>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk,
Linux-arm-toolchain@lists.arm.linux.org.uk
Subject: Re: add new code section for kernel code
Date: Mon, 10 Apr 2006 11:12:54 +0200 [thread overview]
Message-ID: <443A2196.5090306@andric.com> (raw)
In-Reply-To: <20060409203046.GA24461@flint.arm.linux.org.uk>
Russell King wrote:
> Thanks for testing; I've applied this patch so 2.6.17-rc2 onwards will
> have this fixed.
Maybe this can also be applied to the data sections, for people who
compile with -fdata-sections? As in the following patch (note that the
.rodata sections are already wildcarded):
diff -urNd a/arch/arm/boot/compressed/vmlinux.lds.in
b/arch/arm/boot/compressed/vmlinux.lds.in
--- a/arch/arm/boot/compressed/vmlinux.lds.in 2006-03-20
06:53:29.000000000 +0100
+++ b/arch/arm/boot/compressed/vmlinux.lds.in 2006-04-10
11:06:03.000000000 +0200
@@ -34,7 +35,7 @@
.got : { *(.got) }
_got_end = .;
.got.plt : { *(.got.plt) }
- .data : { *(.data) }
+ .data : { *(.data) *(.data.*) }
_edata = .;
. = BSS_START;
next prev parent reply other threads:[~2006-04-10 9:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 12:45 add new code section for kernel code saeed bishara
2006-04-06 13:10 ` Paolo Ornati
2006-04-06 15:27 ` saeed bishara
2006-04-06 16:47 ` saeed bishara
2006-04-07 11:02 ` saeed bishara
2006-04-07 15:14 ` Arjan van de Ven
2006-04-07 15:43 ` Russell King
2006-04-09 9:53 ` saeed bishara
2006-04-09 20:30 ` Russell King
2006-04-10 7:11 ` saeed bishara
2006-04-10 9:12 ` Dimitry Andric [this message]
2006-04-11 14:49 ` saeed bishara
2006-04-12 5:34 ` Arjan van de Ven
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=443A2196.5090306@andric.com \
--to=dimitry@andric.com \
--cc=Linux-arm-toolchain@lists.arm.linux.org.uk \
--cc=arjan@infradead.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@fastwebnet.it \
--cc=saeed.bishara@gmail.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;
as well as URLs for NNTP newsgroup(s).