linux-kernel - linux-next: build failure after merge of the final tree (tip tree related)

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

Date:	Tue, 3 Aug 2010 02:23:10 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, linux-next@...r.kernel.org,
	Russell King <rmk@....linux.org.uk>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: linux-next: build failure after merge of the final tree (tip tree
 related)

Hi all,

Lots (if not all) of the arm builds failed for next-20100802 with these
errors:

arch/arm/mm/init.c: In function 'arm_bootmem_init':
arch/arm/mm/init.c:184: error: implicit declaration of function 'memblock_start_pfn'
arch/arm/mm/init.c:186: error: implicit declaration of function 'memblock_end_pfn'
arch/arm/mm/init.c:188: error: implicit declaration of function 'memblock_size_bytes'

Caused by commit 53e16bfaf19346f59b3502e207aa66c61332075c ("memblock:
Introduce for_each_memblock() and new accessors, and use it") interacting
with commit 2778f62056ada442414392d7ccd41188bb631619 ("ARM: initial LMB
trial") and some others from the arm tree.

Ben, is there no way to retain the old APIs while creating the new ones?
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped