From: Mike Turquette <mturquette@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, 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>
Subject: Re: linux-next: build failure after merge of the samsung tree
Date: Thu, 25 Sep 2014 16:01:24 -0700 [thread overview]
Message-ID: <20140925230124.19023.33551@quantum> (raw)
In-Reply-To: <20140924155336.6e64b952@canb.auug.org.au>
Quoting Stephen Rothwell (2014-09-23 22:53:36)
> 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?
I saw in another thread that Kukjin merged the clk tree into his -next
branch. Is there anything left to do on this one?
Regards,
Mike
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
next prev parent reply other threads:[~2014-09-25 23:01 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
2014-09-25 23:01 ` Mike Turquette [this message]
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=20140925230124.19023.33551@quantum \
--to=mturquette@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=javier.martinez@collabora.co.uk \
--cc=kgene@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).