From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: randconfig failures - MMC + trusted foundations
Date: Sun, 27 Apr 2014 10:32:51 +0100 [thread overview]
Message-ID: <20140427093250.GA26756@n2100.arm.linux.org.uk> (raw)
Last night's omap4430-sdp randconfig build:
In file included from arch/arm/mach-tegra/tegra.c:43:0:
arch/arm/include/asm/trusted_foundations.h: In function 'register_trusted_foundations':
arch/arm/include/asm/trusted_foundations.h:57:2: error: 'setup_max_cpus' undeclared (first use in this function)
Last night's versatile randconfig build:
drivers/mmc/core/core.c: In function 'mmc_card_power_up':
drivers/mmc/core/core.c:1517:4: error: implicit declaration of function 'gpiod_set_value'
This one appears to be a regular feature of failure, and is as I'm
carrying Olof's "mmc: add support for power-on sequencing through DT"
patch for CuBox wireless - see the 222 patch set. It probably points
at something not being right with GPIO stuff.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next reply other threads:[~2014-04-27 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 9:32 Russell King - ARM Linux [this message]
2014-04-27 10:01 ` [PATCH] ARM: trusted_foundations: only set setup_max_cpus if SMP set Alexandre Courbot
2014-05-01 7:22 ` Alexandre Courbot
2014-05-01 16:50 ` Stephen Warren
2014-05-02 1:22 ` Alexandre Courbot
2014-04-27 10:09 ` randconfig failures - MMC + trusted foundations Alexandre Courbot
2014-04-27 10:33 ` Russell King - ARM Linux
2014-04-27 19:46 ` Olof Johansson
2014-04-27 19:54 ` 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=20140427093250.GA26756@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).