linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andy Gross <agross@codeaurora.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build failure after merge of the qcom tree
Date: Fri, 1 Apr 2016 10:28:14 +1100	[thread overview]
Message-ID: <20160401102814.1cf1b302@canb.auug.org.au> (raw)

Hi Andy,

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

ERROR (phandle_references): Reference to non-existent node or label "blsp2_dma"

ERROR (phandle_references): Reference to non-existent node or label "blsp2_dma"

ERROR: Input tree has errors, aborting (use -f to force output)
scripts/Makefile.lib:307: recipe for target 'arch/arm/boot/dts/qcom-msm8974-sony-xperia-honami.dtb' failed

Maybe caused by commit

  423f5fed42fa ("Revert "dts: msm8974: Add blsp2_bam dma node"")

I have used the qcom tree from next-20160331 for today.

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2016-03-31 23:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31 23:28 Stephen Rothwell [this message]
2018-04-25 22:40 linux-next: build failure after merge of the qcom tree 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
2019-04-23 23:25 Stephen Rothwell
2019-04-23 23:50 ` Matthias Kaehlcke
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
2021-10-24 23:43 Stephen Rothwell
2021-10-25  2:37 ` Bjorn Andersson
2022-11-07 22:00 Stephen Rothwell
2022-11-07 22:15 ` Matti Lehtimäki
2022-11-08  1:30 ` Bjorn Andersson
2023-09-20 22:42 Stephen Rothwell
2023-09-21  6:30 ` Luca Weiss
2023-12-03 23:23 Stephen Rothwell
2023-12-03 23:30 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=20160401102814.1cf1b302@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=agross@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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).