From: Mark Brown <broonie@kernel.org>
To: Thierry Reding <treding@nvidia.com>,
Paul Walmsley <paul@pwsan.com>,
Mike Turquette <mturquette@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: next-20150402 build: 3 failures 18 warnings (next-20150402)
Date: Thu, 2 Apr 2015 12:22:31 +0100 [thread overview]
Message-ID: <20150402112231.GQ6023@sirena.org.uk> (raw)
In-Reply-To: <E1YdaYh-0000LL-D5@debutante>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
On Thu, Apr 02, 2015 at 09:33:03AM +0100, Build bot for Mark Brown wrote:
> Failed defconfigs:
> arm64-allmodconfig
For the past few days -next has been failing to build an arm64
allmodconfig due to:
| drivers/built-in.o: In function `tegra124_132_clock_init_post':
| :(.init.text+0x285d8): undefined reference to `tegra_emc_init'
This is triggered by d035fdfa27ac124bc8 (arm64: Add Tegra132 support)
which enables ARCH_TEGRA and ARCH_TEGRA_132_SOC for arm64 which in turn
causes clk-tegra124 to be built on arm64. That driver relies on
TEGRA124_EMC but that depends on ARCH_TEGRA_124_SOC which is 32 bit
only.
We either need the EMC driver for Tegra132, a stub or some ifdefs.
It also looks like there's an issue if the memory controller driver is
not enabled (which looks to be something that can be controlled by the
user) but I've not checked properly.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-04-02 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1YdaYh-0000LL-D5@debutante>
2015-04-02 10:48 ` ARM allmodconfig build failures in -next Mark Brown
2015-04-02 11:22 ` Mark Brown [this message]
2015-04-02 13:50 ` next-20150402 build: 3 failures 18 warnings (next-20150402) Thierry Reding
2015-04-02 22:11 ` Thierry Reding
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=20150402112231.GQ6023@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=paul@pwsan.com \
--cc=treding@nvidia.com \
--cc=will.deacon@arm.com \
/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