All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Chen-Yu Tsai <wens@csie.org>, Yu-Tung Chang <mtwget@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the sunxi tree
Date: Tue, 27 Oct 2020 16:28:51 +0100	[thread overview]
Message-ID: <20201027152851.bndhe5y7hm6lbtjg@gilmour.lan> (raw)
In-Reply-To: <20201027104220.0c8167d0@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 708 bytes --]

Hi Stephen,

On Tue, Oct 27, 2020 at 10:42:20AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the sunxi tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/boot/dts/sun8i-h3-zeropi.dts:53.25-63.4: ERROR (phandle_references): /gmac-3v3: Reference to non-existent node or label "gmac_power_pin_nanopi"
> 
> ERROR: Input tree has errors, aborting (use -f to force output)
> 
> Caused by commit
> 
>   89cfb6d76fdc ("ARM: dts: sun8i: add FriendlyArm ZeroPi support")
> 
> I have reverted that commit for today.

Sorry for that, Yu-Tung sent a fix for it that is now in my branch for
next, so all should be good tomorrow.

Thanks!
Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2020-10-27 15:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 23:42 linux-next: build failure after merge of the sunxi tree Stephen Rothwell
2020-10-27 15:28 ` Maxime Ripard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-22 23:27 Stephen Rothwell
2021-11-23  9:31 ` 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  0:10 ` Stephen Rothwell
2017-03-07 21:39 ` Maxime Ripard
2017-03-07 21:39   ` Maxime Ripard
2017-03-08  8:26   ` Jani Nikula
2017-03-08  8:26     ` Jani Nikula
2017-03-08  9:49     ` Daniel Vetter
2017-03-08  9:49       ` Daniel Vetter
2016-10-25  0:26 Stephen Rothwell
2016-10-25 10:41 ` Maxime Ripard
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=20201027152851.bndhe5y7hm6lbtjg@gilmour.lan \
    --to=maxime@cerno.tech \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mtwget@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=wens@csie.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.