From: Tim Abbott <tabbott@MIT.EDU>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Anders Kaseorg <andersk@mit.edu>, Waseem Daher <wdaher@mit.edu>,
Denys Vlasenko <vda.linux@googlemail.com>,
Jeff Arnold <jbarnold@mit.edu>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Roman Zippel <zippel@linux-m68k.org>,
linux-m68k@vger.kernel.org, Tim Abbott <tabbott@mit.edu>
Subject: [PATCH 0/2] section name cleanup for m68k
Date: Thu, 30 Apr 2009 19:49:21 -0400 [thread overview]
Message-ID: <1241135363-8506-1-git-send-email-tabbott@mit.edu> (raw)
This patch series cleans up the section names on the m68k
architecture. It requires the architecture-independent macro
definitions from this patch series:
<http://www.spinics.net/lists/mips/msg33499.html>
The long-term goal here is to add support for building the kernel with
-ffunction-sections -fdata-sections. This requires renaming all the
magic section names in the kernel of the form .text.foo, .data.foo,
.bss.foo, and .rodata.foo to not have collisions with sections
generated for code like:
static int nosave = 0; /* -fdata-sections places in .data.nosave */
static void head(); /* -ffunction-sections places in .text.head */
Note that these patches have not been boot-tested (aside from testing
the analogous changes on x86), since I don't have access to the
appropriate hardware.
-Tim Abbott
Tim Abbott (2):
m68k: use new macro for .data.cacheline_aligned section.
m68k: use new macros for .data.init_task.
arch/m68k/kernel/process.c | 4 ++--
arch/m68k/kernel/vmlinux-std.lds | 7 ++-----
arch/m68k/kernel/vmlinux-sun3.lds | 2 +-
3 files changed, 5 insertions(+), 8 deletions(-)
next reply other threads:[~2009-04-30 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 23:49 Tim Abbott [this message]
2009-04-30 23:49 ` [PATCH 1/2] m68k: use new macro for .data.cacheline_aligned section Tim Abbott
2009-04-30 23:49 ` [PATCH 2/2] m68k: use new macros for .data.init_task Tim Abbott
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=1241135363-8506-1-git-send-email-tabbott@mit.edu \
--to=tabbott@mit.edu \
--cc=andersk@mit.edu \
--cc=geert@linux-m68k.org \
--cc=jbarnold@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=vda.linux@googlemail.com \
--cc=wdaher@mit.edu \
--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