public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: Broken device trees for exynos in linux-next
Date: Fri, 16 Aug 2013 09:04:28 +0900	[thread overview]
Message-ID: <13b101ce9a14$2cebd700$86c38500$@org> (raw)
In-Reply-To: <CAOesGMgv9gTQ_NtaKZY_ZfLD1NBU19E-vaLaWwmvGJJB1MQrwg@mail.gmail.com>

Olof Johansson wrote:
> 
> Kukjin,
> 
Hi, Olof,

> On Thu, Aug 15, 2013 at 12:34 AM,  <build@lixom.net> wrote:
> 
> >         exynos5440_defconfig:
> > ERROR: Input tree has errors, aborting (use -f to force output)
> >
> >         exynos_defconfig:
> > ERROR: Input tree has errors, aborting (use -f to force output)
> 
> Full error is:
> 
>   DTC     arch/arm/boot/dts/exynos5420-smdk5420.dtb
> 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"
> 
> Looks like you have broken device trees in linux next.

(+ Mark)

NO, the build breakage is due to commit 6187288f15bc ("ARM: dts: exynos5250:
move common i2s properties to exynos5 dtsi" which is in Mark Brown's tree.

Mark, pleaser revert it in your tree...

> Also, what is exynos5440_defconfig?

(+ Arnd)

I think, maybe we discussed about that? :) current exynos_defconfig cannot
support exynos5440 because of LPAE and I remember we decided LPAE and
non-LPAE should be separated. So as I commented before, exynos5440_defconfig
is needed. If you have any concerns, please let me know.

> Don't add contents (which includes defconfigs)
> to linux-next branches that won't make it all the way upstream.
> 
Sure :)

Thanks,
Kukjin

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 16:43 Broken device trees for exynos in linux-next Olof Johansson
2013-08-16  0:04 ` Kukjin Kim [this message]
2013-08-16  0:35   ` Mark Brown
2013-08-16  0:42     ` Mark Brown
2013-08-16  3:34       ` Padma Venkat
2013-08-16 16:04   ` Olof Johansson
2013-08-16 18:03     ` Mark Brown
2013-08-17 10:40     ` Kukjin Kim
2013-08-19 15:15       ` Kevin Hilman
2013-08-22  9:55         ` Kukjin Kim
2013-08-22 16:20           ` Olof Johansson

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='13b101ce9a14$2cebd700$86c38500$@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox