From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kukjin Kim <kgene@kernel•org>
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 15:53:36 +1000 [thread overview]
Message-ID: <20140924155336.6e64b952@canb.auug.org.au> (raw)
In-Reply-To: <00fb01cfd7a4$45eb4a50$d1c1def0$@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
Hi Kukjin,
On Wed, 24 Sep 2014 12:04:36 +0900 Kukjin Kim <kgene@kernel•org> wrote:
>
> > 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?
Mike's clk tree is included in linux-next well after your tree ... and
does Mike's tree get included in the arm-soc tree like your does? So,
clearly you can't build this tree on its own?
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-24 5:53 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
2014-09-24 5:53 ` Stephen Rothwell [this message]
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=20140924155336.6e64b952@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=b.zolnierkie@samsung$(echo .)com \
--cc=javier.martinez@collabora$(echo .)co.uk \
--cc=kgene@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mturquette@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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