linux-kernel - Re: [PATCH v4 7/7] m68knommu: Split the .init section into INIT_TEXT_SECTION and INIT_DATA

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]

Message-ID: <20091030113512.GB26667@merkur.ravnborg.org>
Date:	Fri, 30 Oct 2009 12:35:12 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Tim Abbott <tabbott@...lice.com>
Cc:	Greg Ungerer <gerg@...pgear.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 7/7] m68knommu: Split the .init section into
	INIT_TEXT_SECTION and INIT_DATA_SECTION.

On Thu, Oct 29, 2009 at 09:30:37PM -0400, Tim Abbott wrote:
> On Fri, 30 Oct 2009, Greg Ungerer wrote:
> 
> > Hi Tim,
> > 
> > The whole series applied and ran fine for me!
> > (Of course excepting the define name clash in 1/7)
> 
> Thanks for your patience debugging this patch series!
> 
> > Do you want me to push these into m68knommu.git?
> 
> Yes, that'd be great.  Do you expect these to end up in 2.6.32?  I have an 
> API change to INIT_DATA_SECTION that I want to put in 2.6.32 to fix a tiny 
> regression on blackfin, and I'd like to know which change is likely to get 
> merged first (since the API change will likely conflict).

Let's postpone this fix until merge window opens.
I doubt it has any real effect anyway.

And I'm glad the m68knommu stuff is fixed now.

	Sam
--
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/