From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the sunxi tree
Date: Tue, 25 Oct 2016 12:41:39 +0200 [thread overview]
Message-ID: <20161025104139.t62j4ccqsk7mq4ky@lukather> (raw)
In-Reply-To: <20161025112628.44493fd6@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
On Tue, Oct 25, 2016 at 11:26:28AM +1100, Stephen Rothwell wrote:
> Hi Maxime,
>
> After merging the sunxi tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> ERROR (phandle_references): Reference to non-existent node or label "pwm1_pins_a"
> ERROR: Input tree has errors, aborting (use -f to force output)
> scripts/Makefile.lib:313: recipe for target 'arch/arm/boot/dts/ntc-gr8-chip-pro.dtb' failed
>
> Caused by commit
>
> f49f86fa3b49 ("ARM: gr8: Add CHIP Pro support")
>
> I have used the sunxi tree from next-20161024 for today.
Ugh, sorry for that. The commit is fixed now...
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-10-25 10:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 0:26 linux-next: build failure after merge of the sunxi tree Stephen Rothwell
2016-10-25 10:41 ` Maxime Ripard [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-28 11:38 Stephen Rothwell
2021-11-22 23:27 Stephen Rothwell
2021-11-23 9:31 ` Maxime Ripard
2020-10-26 23:42 Stephen Rothwell
2020-10-27 15:28 ` Maxime Ripard
2020-01-06 22:20 Stephen Rothwell
2020-01-06 22:27 ` Maxime Ripard
2018-06-27 22:42 Stephen Rothwell
2018-03-07 22:35 Stephen Rothwell
2018-03-08 2:37 ` Emmanuel Vadot
2018-03-08 3:19 ` Chen-Yu Tsai
2017-10-31 20:43 Stephen Rothwell
2017-11-01 7:57 ` Corentin Labbe
2017-03-07 0:10 Stephen Rothwell
2017-03-07 21:39 ` Maxime Ripard
2017-03-08 8:26 ` Jani Nikula
2017-03-08 9:49 ` Daniel Vetter
2016-02-04 23:14 Stephen Rothwell
2016-02-05 9:10 ` Maxime Ripard
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=20161025104139.t62j4ccqsk7mq4ky@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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