linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org,
	Roman Zippel <zippel@linux-m68k.org>
Subject: [patch 07/10] m68k: Dont include RODATA into text segment
Date: Sun, 12 Aug 2007 11:40:57 +0200	[thread overview]
Message-ID: <20070812094119.026287596@mail.of.borg> (raw)
In-Reply-To: 20070812094050.522858761@mail.of.borg

[-- Attachment #1: m68k-do-not-include-RODATA-in-text-segment.diff --]
[-- Type: text/plain, Size: 1226 bytes --]

From: Roman Zippel <zippel@linux-m68k.org>

Don't include RODATA into text segment as it includes the kallsyms data
and can cause spurious link failures (layout differences can change the
number of symbols in kallsyms, i.e. when a symbol is equal to _etext it's
not included).

Signed-off-by: Roman Zippel <zippel@linux-m68k.org>
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
---
 arch/m68k/kernel/vmlinux-std.lds |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- a/arch/m68k/kernel/vmlinux-std.lds
+++ b/arch/m68k/kernel/vmlinux-std.lds
@@ -19,6 +19,8 @@ SECTIONS
 	*(.gnu.warning)
 	} :text = 0x4e75
 
+  _etext = .;			/* End of text section */
+
   . = ALIGN(16);		/* Exception table */
   __start___ex_table = .;
   __ex_table : { *(__ex_table) }
@@ -26,8 +28,6 @@ SECTIONS
 
   RODATA
 
-  _etext = .;			/* End of text section */
-
   .data : {			/* Data */
 	DATA_DATA
 	CONSTRUCTORS

-- 
Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


  parent reply	other threads:[~2007-08-12  9:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-12  9:40 [patch 00/10] m68k patches for 2.6.23-rc2 Geert Uytterhoeven
2007-08-12  9:40 ` [patch 01/10] m68k: <asm/page.h> needs <linux/compiler.h> Geert Uytterhoeven
2007-08-12  9:40 ` [patch 02/10] m68k: Kill superfluous extern Geert Uytterhoeven
2007-08-12  9:40 ` [patch 03/10] m68k: Remove unnecessary m68k_memoffset export and init Geert Uytterhoeven
2007-08-12  9:40 ` [patch 04/10] remove dead code in via-pmu68k Geert Uytterhoeven
2007-08-12  9:40 ` [patch 05/10] m68k: Use _AC() instead of #ifdef __ASSEMBLY__ Geert Uytterhoeven
2007-08-12  9:40 ` [patch 06/10] m68k: Enable arbitary speed tty support Geert Uytterhoeven
2007-08-12  9:40 ` Geert Uytterhoeven [this message]
2007-08-12  9:40 ` [patch 08/10] m68k: Fix a few hickups in drivers/scsi/Kconfig Geert Uytterhoeven
2007-08-12  9:40 ` [patch 09/10] zorro: Make sysfs `config attribute read-only Geert Uytterhoeven
2007-08-12  9:41 ` [patch 10/10] m68k/mac: Make mac_hid_mouse_emulate_buttons() declaration visible Geert Uytterhoeven
2007-08-13 12:36   ` Michael Schmitz
2007-08-13 13:09     ` Finn Thain
2007-08-13 13:35       ` Michael Schmitz
2007-08-13 13:57         ` Geert Uytterhoeven

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=20070812094119.026287596@mail.of.borg \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zippel@linux-m68k.org \
    /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).