From: Sylwester Nawrocki <s.nawrocki@samsung•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Krzysztof Kozlowski <krzk@kernel•org>
Subject: Re: linux-next: build failure after merge of the clk-samsung tree
Date: Thu, 26 Apr 2018 12:26:09 +0200 [thread overview]
Message-ID: <1a16ef47-ad28-5fc3-a06f-7bd21fd463ea@samsung.com> (raw)
In-Reply-To: <20180426091940.16bb1faf@canb.auug.org.au>
Hi Stephen,
On 04/26/2018 01:19 AM, Stephen Rothwell wrote:
> After merging the clk-samsung tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> In file included from arch/arm/boot/dts/exynos5440-sd5v1.dts:10:0:
> arch/arm/boot/dts/exynos5440.dtsi:9:10: fatal error: dt-bindings/clock/exynos5440.h: No such file or directory
> #include <dt-bindings/clock/exynos5440.h>
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Caused by commit
>
> f986c0e40ff5 ("clk: samsung: Remove support for Exynos5440")
>
> I used the version of the clk-samsung tree from next-20180424 for today.
My apologies, somehow I didn't notice the build break earlier.
I drop the above mentioned commit from the for-next branch for now.
--
Regards,
Sylwester
prev parent reply other threads:[~2018-04-26 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180425232126epcas2p1e5673f9dfc42c5e8c5e05acb70a6e352@epcas2p1.samsung.com>
2018-04-25 23:19 ` linux-next: build failure after merge of the clk-samsung tree Stephen Rothwell
2018-04-26 7:29 ` Krzysztof Kozlowski
2018-04-26 10:32 ` Sylwester Nawrocki
2018-04-26 10:26 ` Sylwester Nawrocki [this message]
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=1a16ef47-ad28-5fc3-a06f-7bd21fd463ea@samsung.com \
--to=s.nawrocki@samsung$(echo .)com \
--cc=krzk@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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