linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-next@vger.kernel.org, Russell King <rmk@arm.linux.org.uk>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: linux-next: build failure after merge of the final tree (tip tree related)
Date: Tue, 3 Aug 2010 02:23:10 +1000	[thread overview]
Message-ID: <20100803022310.bec3ba79.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 853 bytes --]

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@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2010-08-02 16:23 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 16:23 Stephen Rothwell [this message]
2010-08-02 16:28 ` linux-next: build failure after merge of the final tree (tip tree related) Russell King
2010-08-02 16:32   ` H. Peter Anvin
2010-08-03  1:07     ` Benjamin Herrenschmidt
2010-08-03  1:42   ` Benjamin Herrenschmidt
2010-08-03  3:13     ` H. Peter Anvin
2010-08-03  4:32       ` Benjamin Herrenschmidt
2010-08-03  5:29     ` Ingo Molnar
2010-08-02 16:28 ` Stephen Rothwell
2010-08-03  1:41 ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2011-04-12  4:00 Stephen Rothwell
2011-04-12  6:20 ` Ingo Molnar
2011-04-12  6:25   ` David Miller
2010-11-29  2:50 Stephen Rothwell
2010-11-29 22:30 ` Peter Zijlstra
2010-12-07  1:56 ` Stephen Rothwell
2010-11-22  2:39 Stephen Rothwell
2010-11-22 22:00 ` Don Zickus
2010-11-29  2:50 ` Stephen Rothwell
2010-11-29  8:29   ` Ingo Molnar
2010-11-29 14:30     ` Don Zickus
2010-12-07  1:58       ` Stephen Rothwell
2010-12-07 15:37         ` Don Zickus
2010-10-14  5:49 Stephen Rothwell
2010-10-14  6:31 ` Ingo Molnar
2010-09-13 14:29 Stephen Rothwell
2010-09-16  6:32 ` Stephen Rothwell
2010-09-16  6:39   ` Ingo Molnar
2010-09-16  7:08     ` Russell King - ARM Linux
2010-09-16  7:34       ` Ingo Molnar
2010-09-16  9:02         ` Russell King - ARM Linux
2010-09-16  7:09     ` Stephen Rothwell
2010-09-16  7:20       ` Yinghai Lu
2010-09-16  7:27         ` Stephen Rothwell
2010-09-13 14:06 Stephen Rothwell
2010-09-13 19:17 ` Matt Fleming
2010-09-13 19:22   ` Peter Zijlstra
2010-06-23 16:31 Stephen Rothwell
2010-06-23 16:55 ` Frederic Weisbecker
2010-06-23 23:31   ` Stephen Rothwell
2010-06-24  0:37     ` Stephen Rothwell
2010-06-23  0:50 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100803022310.bec3ba79.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=benh@kernel.crashing.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).