All of lore.kernel.org
 help / color / mirror / Atom feed
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: build failures on Exynos
Date: Fri, 16 Aug 2013 09:18:20 +0900	[thread overview]
Message-ID: <13b301ce9a16$1ce01a90$56a04fb0$@org> (raw)
In-Reply-To: <8738qblxf0.fsf@kernel.org>

Kevin Hilman wrote:
> 
> Hi Kukjin,
> 
Hi,

> The following new build failures started showing up in linux-next
> (next-20130814) when building  the exynos defconfigs below:
> 
> 	arm-exynos5440_defconfig
> ERROR (phandle_references): Reference to non-existent node or label
> "pdma1"
> ERROR (phandle_references): Reference to non-existent node or label
> "pdma1"
> ERROR (phandle_references): Reference to non-existent node or label
> "pdma0"
> ERROR (phandle_references): Reference to non-existent node or label
> "pdma0"
> ERROR: Input tree has errors, aborting (use -f to force output)
> 
> 	arm-exynos_defconfig
> ERROR (phandle_references): Reference to non-existent node or label
> "pdma1"
> ERROR (phandle_references): Reference to non-existent node or label
> "pdma1"
> ERROR (phandle_references): Reference to non-existent node or label
> "pdma0"
> ERROR (phandle_references): Reference to non-existent node or label
> "pdma0"
> ERROR: Input tree has errors, aborting (use -f to force output)
> 
Thanks for your information.

I think it is due to commit 6187288f15bc ("ARM: dts: exynos5250: move common
i2s properties to exynos5 dtsi") which is in Mark Brown's tree. Note, I
added him in Cc in other mail thread from Olof just now.

Thanks again.

- Kukjin

      reply	other threads:[~2013-08-16  0:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 22:28 linux-next: build failures on Exynos Kevin Hilman
2013-08-16  0:18 ` Kukjin Kim [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='13b301ce9a16$1ce01a90$56a04fb0$@org' \
    --to=kgene@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.