From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org
Subject: Re: New randconfig build failures in OMAP
Date: Wed, 6 Jun 2012 01:11:27 -0700 [thread overview]
Message-ID: <20120606081126.GT12766@atomide.com> (raw)
In-Reply-To: <20120605220214.GA29782@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [120605 15:07]:
> I pulled Linus' tree at 7am UTC, and reran the builds after updating
> the build tree with that (plus my pending devel stuff). The resulting
> randconfig spat out this:
>
> arch/arm/mach-omap2/dsp.c: In function 'omap_dsp_reserve_sdram_memblock':
> arch/arm/mach-omap2/dsp.c:58: error: implicit declaration of function 'arm_memblock_steal'
>
> Looks to me like a missing include?
Yup I've caused that one by moving the code around without the memblock.h
include. Looks like I did not hit this one yet with my randconfigs as it's
behind CONFIG_STAGING. Will post a fix along with few other randconfig
fixes.
TOny
prev parent reply other threads:[~2012-06-06 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 22:02 New randconfig build failures in OMAP Russell King - ARM Linux
2012-06-06 1:25 ` Sebastian Reichel
2012-06-06 8:11 ` Tony Lindgren [this message]
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=20120606081126.GT12766@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.