[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1241135661-9147-1-git-send-email-tabbott@mit.edu>
Date: Thu, 30 Apr 2009 19:54:15 -0400
From: Tim Abbott <tabbott@....EDU>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Linux kernel mailing list <linux-kernel@...r.kernel.org>,
Anders Kaseorg <andersk@....edu>,
Waseem Daher <wdaher@....edu>,
Denys Vlasenko <vda.linux@...glemail.com>,
Jeff Arnold <jbarnold@....edu>,
David Howells <dhowells@...hat.com>,
Tim Abbott <tabbott@....edu>
Subject: [PATCH 0/6] section name cleanup for mn10300
This patch series cleans up the section names on the mn10300
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 (6):
mn10300: Use macros for .bss.page_aligned section.
mn10300: Drop unused .data.idt section.
mn10300: use NOSAVE_DATA macro for .data.nosave section.
mn10300: use new macro for .data.cacheline_aligned section.
mn10300: use new macros for .data.init_task.
mn10300: use new macro for .data.read_mostly section.
arch/mn10300/kernel/init_task.c | 3 +--
arch/mn10300/kernel/vmlinux.lds.S | 29 ++++++-----------------------
2 files changed, 7 insertions(+), 25 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists