public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andy Gross <andy.gross@linaro•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Matthias Kaehlcke <mka@chromium•org>,
	Douglas Anderson <dianders@chromium•org>,
	Stephen Boyd <swboyd@chromium•org>
Subject: linux-next: build failure after merge of the qcom tree
Date: Wed, 24 Apr 2019 09:25:31 +1000	[thread overview]
Message-ID: <20190424092531.3988850d@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

Hi all,

After merging the qcom tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

arch/arm/boot/dts/qcom-apq8064.dtsi:1297.29-1309.5: ERROR (phandle_references): /soc/dsi-phy@4700200: Reference to non-existent node or label "xo_board"

Caused by commit

  3560af5a56b5 ("ARM: dts: qcom-apq8064: Set 'xo_board' as ref clock of the DSI PHY")

I have used the version of the qcom tree from next-20190423 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-04-23 23:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 23:25 Stephen Rothwell [this message]
2019-04-23 23:50 ` linux-next: build failure after merge of the qcom tree Matthias Kaehlcke
  -- strict thread matches above, loose matches on Subject: below --
2024-08-01 23:48 Stephen Rothwell
2024-08-05  6:39 ` Satya Priya Kakitapalli (Temp)
2024-06-25 11:36 Mark Brown
2024-07-01  1:22 ` Stephen Rothwell
2023-12-03 23:30 Stephen Rothwell
2023-12-03 23:23 Stephen Rothwell
2023-09-20 22:42 Stephen Rothwell
2023-09-21  6:30 ` Luca Weiss
2022-11-07 22:00 Stephen Rothwell
2022-11-07 22:15 ` Matti Lehtimäki
2022-11-08  1:30 ` Bjorn Andersson
2021-10-24 23:43 Stephen Rothwell
2021-10-25  2:37 ` Bjorn Andersson
2020-04-15  0:41 Stephen Rothwell
2020-04-15  1:18 ` John Stultz
2020-04-20 23:29   ` Stephen Rothwell
2020-04-21  2:41     ` John Stultz
2020-05-18  5:16       ` Stephen Rothwell
2020-05-18  6:19         ` Bjorn Andersson
2018-04-25 22:40 Stephen Rothwell
2018-04-26  3:39 ` Evan Green
2018-04-26  4:52   ` Stephen Rothwell
2018-04-26 16:42     ` Evan Green
2018-04-26 21:23       ` Andy Gross
2016-03-31 23:28 Stephen Rothwell

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=20190424092531.3988850d@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=andy.gross@linaro$(echo .)org \
    --cc=dianders@chromium$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mka@chromium$(echo .)org \
    --cc=swboyd@chromium$(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