linux-kernel - Re: Section mismatches in memblock

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] [day] [month] [year] [list]

Message-ID: <20101008081604.GB13754@elte.hu>
Date:	Fri, 8 Oct 2010 10:16:04 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"H. Peter Anvin" <hpa@...nel.org>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Section mismatches in memblock


* H. Peter Anvin <hpa@...nel.org> wrote:

> On 10/05/2010 07:30 PM, H. Peter Anvin wrote:
> > 
> > Wrong functions!  Furhtermore, at least the tip tree definitely does not
> > have __init_memblock here:
> > 
> 
> Nevermind.  I had missed that Ingo had put stuff into core/memblock on
> top of x86/memblock, just to be confusing.

Correct - we better keep it as a generic, non-x86 topic as it affects 
other architectures. We can zap x86/memblock (it's fully contained in 
core/memblock) so that it's not confusing.

Thanks,

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