From: Al Viro <viro@ftp.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org
Subject: [PATCH 3/3] m68k: compile fix - updated vmlinux.lds to include LOCK_TEXT
Date: Thu, 15 Dec 2005 09:00:37 +0000 [thread overview]
Message-ID: <20051215090037.GV27946@ftp.linux.org.uk> (raw)
... and that should get m68k to build with gcc 3.x in mainline. gcc4
fixes are separate story.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---
[rz: BTW, proposed variant of thread_info patchset is available for review,
see ftp.linux.org.uk/pub/people/viro/task_thread_info-mbox... Doesn't
do any incompatible changes, mergable at leisure, reduces the remaining
renaming to ~50 lines - the only chunk that will have to go at 2.6.16...]
arch/m68k/kernel/vmlinux-std.lds | 1 +
arch/m68k/kernel/vmlinux-sun3.lds | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)
cc448b2f798627bc448ca14f3d6fb39f356bb117
diff --git a/arch/m68k/kernel/vmlinux-std.lds b/arch/m68k/kernel/vmlinux-std.lds
index e58654f..69d1d3d 100644
--- a/arch/m68k/kernel/vmlinux-std.lds
+++ b/arch/m68k/kernel/vmlinux-std.lds
@@ -13,6 +13,7 @@ SECTIONS
.text : {
*(.text)
SCHED_TEXT
+ LOCK_TEXT
*(.fixup)
*(.gnu.warning)
} :text = 0x4e75
diff --git a/arch/m68k/kernel/vmlinux-sun3.lds b/arch/m68k/kernel/vmlinux-sun3.lds
index cc37e8d..f814e66 100644
--- a/arch/m68k/kernel/vmlinux-sun3.lds
+++ b/arch/m68k/kernel/vmlinux-sun3.lds
@@ -14,6 +14,7 @@ SECTIONS
*(.head)
*(.text)
SCHED_TEXT
+ LOCK_TEXT
*(.fixup)
*(.gnu.warning)
} :text = 0x4e75
--
0.99.9.GIT
next reply other threads:[~2005-12-15 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 9:00 Al Viro [this message]
2005-12-15 12:49 ` [PATCH 3/3] m68k: compile fix - updated vmlinux.lds to include LOCK_TEXT Roman Zippel
2005-12-15 13:12 ` Roman Zippel
2005-12-15 16:19 ` Al Viro
2005-12-19 15:18 ` Roman Zippel
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=20051215090037.GV27946@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@osdl.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