From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the clk-samsung tree
Date: Thu, 26 Apr 2018 12:32:06 +0200 [thread overview]
Message-ID: <c5139744-ca32-cfaf-c79a-f718ddd3c3f9@samsung.com> (raw)
In-Reply-To: <CAJKOXPexiwOyPwmAV8KQj4JAnWHYYP4o8eVYodhvRYfKFGVbNw@mail.gmail.com>
On 04/26/2018 09:29 AM, Krzysztof Kozlowski wrote:
> On Thu, Apr 26, 2018 at 1:19 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> After merging the clk-samsung tree, today's linux-next build (arm
>> multi_v7_defconfig) failed like this:
[...]
>> Caused by commit
>>
>> f986c0e40ff5 ("clk: samsung: Remove support for Exynos5440")
>>
>> I used the version of the clk-samsung tree from next-20180424 for today.
>
> Thanks for the report, kbuild also mentioned this. The DTS which are
> using this header are removed in first patch of patchset... which was
> not applied yet and anyway would end in different tree. I think the
> patch removing clk header should wait till DTS change get merged into
> mainline.
Yes, let's remove all related dts parts first and then drivers in
subsequent release.
--
Regards,
Sylwester
next prev parent reply other threads:[~2018-04-26 10:32 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 ` Stephen Rothwell
2018-04-26 7:29 ` Krzysztof Kozlowski
[not found] ` <CGME20180426103215epcas2p32c60d927d618a82075b051b1f0624216@epcas2p3.samsung.com>
2018-04-26 10:32 ` Sylwester Nawrocki [this message]
2018-04-26 10:26 ` Sylwester Nawrocki
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=c5139744-ca32-cfaf-c79a-f718ddd3c3f9@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-samsung-soc@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
all inboxes | Powered by JetHome®