linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] DaVinci dts updates for v4.9
Date: Thu, 15 Sep 2016 14:11:03 +0530	[thread overview]
Message-ID: <211a1af8-d76b-62af-08ac-a374d3285c0a@ti.com> (raw)
In-Reply-To: <3347114.RAnckMhlMa@wuerfel>

Hi Arnd,

On Wednesday 14 September 2016 09:23 PM, Arnd Bergmann wrote:
> On Wednesday, August 24, 2016 4:30:05 PM CEST Sekhar Nori wrote:
>> DaVinci DA850 device-tree enhancements include:
>>
>> - Support for new board OMAP-L138 LCDK
>> - Add AEMIF node on DA850 EVM and use it for NAND
>> - Audio support for LCDK
>> - Cleanups for PWM and UART
>>
>>
> 
> This one fails to build:
> 
> 
> ERROR (phandle_references): Reference to non-existent node or label "nand_cs3_pins"
> 
> ERROR: Input tree has errors, aborting (use -f to force output)
>   DTC     arch/arm/boot/dts/bcm47081-asus-rt-n18u.dtb
> 
> 
> Can you send a fixed version please?

Did the merge happen cleanly? There should be no nand_cs3_pins if the
merge was clean. It should be removed with 31e3a8817b66 ("ARM: dts:
da850,da850-evm: Add an aemif node and use it for the NAND").

If the merge was clean, can you please push the offending tree to some
place I can fetch and take a look. I dont have "nand_cs3_pins" in my
tree anymore nor I can reproduce the build break.

Thanks,
Sekhar

  reply	other threads:[~2016-09-15  8:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 11:00 [GIT PULL 1/3] DaVinci soc support updates for v4.9 Sekhar Nori
2016-08-24 11:00 ` [GIT PULL 2/3] DaVinci dts " Sekhar Nori
2016-09-14 15:53   ` Arnd Bergmann
2016-09-15  8:41     ` Sekhar Nori [this message]
2016-09-15  9:35       ` Arnd Bergmann
2016-08-24 11:00 ` [GIT PULL 3/3] DaVinci defconfig " Sekhar Nori
2016-09-02 15:45   ` Arnd Bergmann
2016-09-02 16:21 ` [GIT PULL 1/3] DaVinci soc support " Arnd Bergmann

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=211a1af8-d76b-62af-08ac-a374d3285c0a@ti.com \
    --to=nsekhar@ti.com \
    --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).