linux-kernel - Re: [PATCH 1/7] Make section names compatible with -ffunction-sections -fdata-sections

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 1 Jan 2009 08:32:30 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Tim Abbott <tabbott@....EDU>
Cc:	Andi Kleen <andi@...stfloor.org>, Jeff Arnold <jbarnold@....EDU>,
	linux-kernel@...r.kernel.org,
	Denys Vlasenko <vda.linux@...glemail.com>,
	Anders Kaseorg <andersk@....EDU>,
	Waseem Daher <wdaher@....EDU>,
	Nikanth Karthikesan <knikanth@...e.de>
Subject: Re: [PATCH 1/7] Make section names compatible with
 -ffunction-sections -fdata-sections

On Wed, 31 Dec 2008 16:59:39 -0500 (EST) Tim Abbott <tabbott@....EDU> wrote:

> Hi Andrew,
> 
> I'd like to get this -ffunction-sections patch merged sometime during the 
> 2.6.29 merge window.  I've updated it in my git repository to work on top 
> of Linus' current master; how do you want to handle this?
> 

<tries to remember what the patch does, and what the problem with it is>
<finds it>

OK, it hits a lot of files in minor ways.

You could ask Linus to merge it late in the -rc1 merge window (please
cc me on the email).  Or you could just send it to me (with the usual
cc's) and I'll toss it into my 2.6.29-rc1 pile.  I doubt if it'll cause
much trouble.  But please do check its applicability to linux-next - people
have been moving arch files into different directories lately.
--
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/