Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756796AbZD3Xn4 (ORCPT ); Thu, 30 Apr 2009 19:43:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752710AbZD3Xnq (ORCPT ); Thu, 30 Apr 2009 19:43:46 -0400 Received: from BISCAYNE-ONE-STATION.MIT.EDU ([18.7.7.80]:58791 "EHLO biscayne-one-station.mit.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753541AbZD3Xnp (ORCPT ); Thu, 30 Apr 2009 19:43:45 -0400 From: Tim Abbott To: Sam Ravnborg Cc: Linux kernel mailing list , Anders Kaseorg , Waseem Daher , Denys Vlasenko , Jeff Arnold , Bryan Wu , uclinux-dist-devel@blackfin.uclinux.org, Tim Abbott Subject: [PATCH] section name cleanup for blackfin Date: Thu, 30 Apr 2009 19:43:34 -0400 Message-Id: <1241135015-7860-1-git-send-email-tabbott@mit.edu> X-Mailer: git-send-email 1.6.2.1 X-Spam-Flag: NO X-Spam-Score: 0.00 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1240 Lines: 33 This patch series cleans up the section names on the blackfin architecture. It requires the architecture-independent macro definitions from this patch series: 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 (1): blackfin: use new macro for .data.cacheline_aligned section. arch/blackfin/kernel/vmlinux.lds.S | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/