From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754699Ab0CIP5R (ORCPT ); Tue, 9 Mar 2010 10:57:17 -0500 Received: from mail-gw0-f46.google.com ([74.125.83.46]:62093 "EHLO mail-gw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751455Ab0CIP5M convert rfc822-to-8bit (ORCPT ); Tue, 9 Mar 2010 10:57:12 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=p53LkOvMjlnVkt6De4adqMsbEwkosYcE9Ry0Ji6WxAR3E/vPvbrk63FQO3tpFG/MQk ow2WEgILf5pu3bFCOCeHIBS5jduOA9ICTiFL1XkyBO3+floHMJmbu89FL27YPhq+Z2Vz MS2r7/ObJW/vrJr0RJKldFWlcBH0aTp8jPldM= MIME-Version: 1.0 In-Reply-To: References: <1266624237-22372-1-git-send-email-vda.linux@googlemail.com> From: Mike Frysinger Date: Tue, 9 Mar 2010 10:56:51 -0500 Message-ID: <8bd0f97a1003090756u28e6f3bdpd44b8fce15f92ac1@mail.gmail.com> Subject: Re: [PATCH 00/24] Rename kernel's magic sections for compatibility with -ffunction-sections -fdata-sections To: Tim Abbott Cc: Michal Marek , Denys Vlasenko , Sam Ravnborg , Haavard Skinnemoen , David Howells , linux-kernel@vger.kernel.org, Bjorn Wesen , Tim Bird , Anders Kaseorg , Waseem Daher , Rusty Russell , Andi Kleen , Stephen Rothwell , "H. Peter Anvin" , Barry Song , Mike Frysinger Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Feb 28, 2010 at 23:03, Tim Abbott wrote: > On Sat, 20 Feb 2010, Denys Vlasenko wrote: >> Here is a new version of the -ffunction-sections -fdata-sections patch >> series based on current Linus tree. > > Aside from patch 17, which I would prefer that Haavard review, these > patches look correct (and patch 17 can be safely dropped).  Please > consider the rest of Denys' patches in this patch series > > Acked-by: Tim Abbott > > The patches still apply fine on Linus' current master.  There are no merge > conflicts with linux-next's current master, but we will need to do > something to merge with > > "Blackfin: initial XIP support" > > in linux-next, which introduces a direct reference to .data.percpu.* (not > using the normal PERCPU macros so they can put .data.percpu content inside > the .init.data section).  That conflict looks easy to deal with by adding > a new macro to handle this case (CCing the author and blackfin maintainer; > it's possible that this blackfin patch is going in soon, in which case we > can just rebase these patches on top). > > Michal, what are your thoughts on this patch series?  The kbuild tree > would be a reasonable path for merging these patches. ive posted this patch for merging via the Blackfin tree now, so hopefully it'll be in soon -mike