From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: LMB build failure in -next
Date: Fri, 16 Jul 2010 10:54:18 +0100 [thread overview]
Message-ID: <20100716095418.GB17952@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100716094151.GI9082@rakim.wolfsonmicro.main>
On Fri, Jul 16, 2010 at 10:41:51AM +0100, Mark Brown wrote:
> In -next the patch 'ARM: initial LMB trial' is causing build failures:
>
> CHECK arch/arm/kernel/setup.c
> arch/arm/kernel/setup.c:30:11: error: unable to open 'linux/lmb.h'
>
> for me. Looks like the generic header got missed from the commit or
> there's some other tree that also needs to be in -next?
Ben asked Linus to pull his LMB updates, which renamed all the LMB
infrastructure to memblock. I'll have to rebase the LMB branch -
possibly later today.
next prev parent reply other threads:[~2010-07-16 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 9:41 LMB build failure in -next Mark Brown
2010-07-16 9:54 ` Russell King - ARM Linux [this message]
2010-07-16 9:59 ` Mark Brown
2010-07-16 10:19 ` Russell King - ARM Linux
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=20100716095418.GB17952@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).