From: Kukjin Kim <kgene@kernel.org>
To: 'Stephen Rothwell' <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
'Javier Martinez Canillas' <javier.martinez@collabora.co.uk>,
'Bartlomiej Zolnierkiewicz' <b.zolnierkie@samsung.com>,
'Mike Turquette' <mturquette@linaro.org>
Subject: RE: linux-next: build failure after merge of the samsung tree
Date: Wed, 24 Sep 2014 12:04:36 +0900 [thread overview]
Message-ID: <00fb01cfd7a4$45eb4a50$d1c1def0$@kernel.org> (raw)
In-Reply-To: <20140924110836.209bc8e2@canb.auug.org.au>
Stephen Rothwell wrote:
>
> Hi Kukjin,
>
Hi Stephen,
> After merging the samsung tree, today's linux-next build (arm multi_v7_defconfig)
> failed like this:
>
> arch/arm/boot/dts/exynos5250-snow.dts:13:46: fatal error: dt-bindings/clock/maxim,max77686.h: No such
> file or directory
> #include <dt-bindings/clock/maxim,max77686.h>
> ^
>
+ Mike
Hmm... I think, inclusion of the header file should be included in Mike's clk
tree...What's wrong?
> Caused by commit c04c92ed5614 ("ARM: dts: Add rtc_src clk for s3c-rtc on exynos5250-snow").
>
> In file included from arch/arm/mach-tegra/cpuidle-tegra114.c:17:0:
> arch/arm/mach-tegra/cpuidle-tegra114.c: In function 'tegra114_idle_power_down':
> arch/arm/include/asm/firmware.h:64:24: error: too few arguments to function 'firmware_ops->do_idle'
> ((firmware_ops->op) ? firmware_ops->op(__VA_ARGS__) : (-ENOSYS))
> ^
> arch/arm/mach-tegra/cpuidle-tegra114.c:52:6: note: in expansion of macro 'call_firmware_op'
> if (call_firmware_op(do_idle) == -ENOSYS)
> ^
>
> Caused by commit f5217f3b9332 ("ARM: EXYNOS: add AFTR mode support to
> firmware do_idle method").
OK, I'll revert it firstly. Thanks.
>
> I have used the samsung tree from next-20140923 for today.
OK.
- Kukjin
next prev parent reply other threads:[~2014-09-24 3:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 1:08 linux-next: build failure after merge of the samsung tree Stephen Rothwell
2014-09-24 3:04 ` Kukjin Kim [this message]
2014-09-24 5:53 ` Stephen Rothwell
2014-09-25 23:01 ` Mike Turquette
2014-09-26 0:43 ` Stephen Rothwell
2014-09-24 3:54 ` Kukjin Kim
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='00fb01cfd7a4$45eb4a50$d1c1def0$@kernel.org' \
--to=kgene@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sfr@canb.auug.org.au \
/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).