linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: javier.martinez@collabora.co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: build failure after merge of the arm-soc tree
Date: Fri, 03 Oct 2014 08:50:09 +0200	[thread overview]
Message-ID: <542E4721.8040300@collabora.co.uk> (raw)
In-Reply-To: <14357384.nIoLZkacVq@wuerfel>

Hello Arnd, Stephen,

On 10/02/2014 04:32 PM, Arnd Bergmann wrote:
> On Thursday 02 October 2014 11:37:42 Stephen Rothwell wrote:
>> After merging the arm-soc 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>
>>                                               ^
>> 
>> Caused by commit c04c92ed5614 ("ARM: dts: Add rtc_src clk for s3c-rtc
>> on exynos5250-snow").
>> 
>> Presumably there is some dependency on some tree that someone has
>> forgotten to merge 
>> 
>> I reverted that commit for today.
>> 
>> Which then got to:
>> 
>> /scratch/sfr/next/arch/arm/boot/dts/exynos5420-peach-pit.dts:15:46: fatal error: dt-bindings/clock/maxim,max77802.h: No such file or directory
>>  #include <dt-bindings/clock/maxim,max77802.h>
>>                                               ^
>> compilation terminated.
>> /scratch/sfr/next/arch/arm/boot/dts/exynos5800-peach-pi.dts:15:46: fatal error: dt-bindings/clock/maxim,max77802.h: No such file or directory
>>  #include <dt-bindings/clock/maxim,max77802.h>
>>                                               ^
>> compilation terminated.
>> Error: /scratch/sfr/next/arch/arm/boot/dts/hisi-x5hd2.dtsi:417.21-22 syntax error
>> FATAL ERROR: Unable to parse input tree
>> 
>> Caused by 8bd43b6e6df7 ("ARM: dts: Add rtc_src clk for s3c-rtc on
>> exynos Peach boards").
>> 
>> I give up ... please test your trees better ...
> 
> I'm deeply sorry about that. I actually saw the problem here but was too
> tired to fix it up again by redoing all the merges in our next/late
> branch.
> 

I'm so sorry about the breakage, when I posted this patch I mentioned that
it was meant for the 3.18-rc cycle once 3.18-rc1 was released [0]. Because
it fixes a regression caused by a patch queued in the clock tree for 3.18.
I should had been more explicit about the dependencies to avoid confusions.

> I've changed the for-next branch now to drop all of next/late, I think
> we're better off not sending any of it for 3.18, especially as I found
> some other problems as well.
> 

Do you think that it may be possible to send this for the 3.18-rc cycle
or should it have to wait for 3.19? Without this the real time clock does
not work on the Peach Chromebooks and your next/late branch contains other
fixes as well (e.g: the Exynos USB dr_mode DT patches).

>> I have used the arm-soc tree form next-20141001 for today (which still
>> needs 5 reverts to get it to build :-().
> 
> D'oh. I actually fixed these already last friday in the next/dt branch
> but for some reason forgot to include it in for-next.
> I've made sure that everything is included now.
> 
> 	Arnd
>

Thanks a lot and best regards,
Javier

[0]: https://www.mail-archive.com/linux-samsung-soc at vger.kernel.org/msg36702.html

  reply	other threads:[~2014-10-03  6:50 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02  1:37 linux-next: build failure after merge of the arm-soc tree Stephen Rothwell
2014-10-02  2:36 ` Kukjin Kim
2014-10-02 14:32 ` Arnd Bergmann
2014-10-03  6:50   ` Javier Martinez Canillas [this message]
2014-10-03  7:56     ` Russell King - ARM Linux
2014-10-03  8:07       ` Javier Martinez Canillas
  -- strict thread matches above, loose matches on Subject: below --
2023-06-13  0:43 Stephen Rothwell
2023-06-13  6:38 ` Linus Walleij
2023-01-16  5:27 Stephen Rothwell
2023-01-16 10:16 ` Arnd Bergmann
2022-03-01 22:50 Stephen Rothwell
2022-03-02  7:45 ` Arnd Bergmann
2022-03-02  9:52   ` Matthias Brugger
2022-03-03 17:23     ` Arnd Bergmann
2021-10-12  0:03 Stephen Rothwell
2021-10-12  7:35 ` Nicolas Ferre
2021-10-12  7:56   ` Arnd Bergmann
2021-10-12  9:29     ` Nicolas Ferre
2021-04-09 10:13 Stephen Rothwell
2021-04-09 10:56 ` Hector Martin
2020-11-23 22:31 Stephen Rothwell
2020-11-24  9:18 ` Christoph Hellwig
2020-11-24 10:43   ` Maxime Ripard
2019-08-13 22:49 Stephen Rothwell
2019-08-14 10:52 ` Arnd Bergmann
2018-07-15 23:13 Stephen Rothwell
2018-07-15 23:50 ` Olof Johansson
2018-07-16  0:38   ` Olof Johansson
2018-07-16  6:18   ` Robert Jarzmik
2016-04-25 23:43 Stephen Rothwell
2016-04-25 23:54 ` Arnd Bergmann
2016-04-26  0:51   ` Stephen Rothwell
2016-04-26  7:40     ` Arnd Bergmann
2015-12-17  6:40 Stephen Rothwell
2015-10-14 23:19 Stephen Rothwell
2015-10-15  2:40 ` Jisheng Zhang
2015-10-15 15:52   ` Arnd Bergmann
2015-10-15 14:10 ` Arnd Bergmann
2015-08-07  0:33 Stephen Rothwell
2015-06-12  0:30 Michael Ellerman
2015-06-12 18:19 ` Kevin Hilman
2015-04-07  1:12 Stephen Rothwell
2015-04-07  8:43 ` Matthias Brugger
2015-04-07  9:28   ` Linus Walleij
2015-04-07  9:46     ` Matthias Brugger
2015-04-07 12:28     ` Arnd Bergmann
2015-04-08 14:49       ` Linus Walleij
2015-04-08 14:59         ` Matthias Brugger
2015-04-13 23:47           ` Stephen Rothwell
2015-04-14  0:05             ` Arnd Bergmann
2014-09-26  1:55 Stephen Rothwell
2014-09-26  2:57 ` Wei Xu
2014-09-30  0:12 ` Stephen Rothwell
2014-09-30  1:45   ` Wei Xu
2014-03-09 11:55 Mark Brown
2014-03-10 10:45 ` Will Deacon
2014-03-10 11:58   ` Catalin Marinas
2014-03-09 11:41 Mark Brown
2014-03-09 17:08 ` Olof Johansson
2014-03-09 19:08   ` Mark Brown
2013-04-19  6:46 Stephen Rothwell
2013-04-19 14:01 ` Olof Johansson
2013-04-22 13:26   ` Thomas Petazzoni

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=542E4721.8040300@collabora.co.uk \
    --to=javier.martinez@collabora.co.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).