All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Mark Brown <broonie@kernel.org>
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	kernel-build-reports@lists.linaro.org,
	linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: next-20170323 build: 2 failures 4 warnings (next-20170323)
Date: Thu, 23 Mar 2017 08:44:07 -0700	[thread overview]
Message-ID: <m2a88cm20o.fsf@baylibre.com> (raw)
In-Reply-To: <20170323110249.3tf3tjo6c2y5qbkh@sirena.org.uk> (Mark Brown's message of "Thu, 23 Mar 2017 11:02:49 +0000")

Mark Brown <broonie@kernel.org> writes:

> On Thu, Mar 23, 2017 at 07:56:49AM +0000, Build bot for Mark Brown wrote:
>
> Today's -next fails to build an arm64 allmodconfig and defconfig due to:
>
>> 	arm64-allmodconfig
>> 	arm64-defconfig
>> ERROR (phandle_references): Reference to non-existent node or label "pwm_f_clk_pins"
>> ERROR (phandle_references): Reference to non-existent node or label "pwm_ao_a_3_pins"
>> ERROR: Input tree has errors, aborting (use -f to force output)
>
> The offending references are in 3224eaca966088b4cf4f1ca3 (ARM64: dts:
> meson-gxl: add support for the Khadas VIM board), there doesn't seem to
> be anything providing those phandles in either mainline or -next.

This was my fault, I backed it out soon after I committed, but it was
picked up by -next before I removed it.

Sorry for the noise,

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20170323 build: 2 failures 4 warnings (next-20170323)
Date: Thu, 23 Mar 2017 08:44:07 -0700	[thread overview]
Message-ID: <m2a88cm20o.fsf@baylibre.com> (raw)
In-Reply-To: <20170323110249.3tf3tjo6c2y5qbkh@sirena.org.uk> (Mark Brown's message of "Thu, 23 Mar 2017 11:02:49 +0000")

Mark Brown <broonie@kernel.org> writes:

> On Thu, Mar 23, 2017 at 07:56:49AM +0000, Build bot for Mark Brown wrote:
>
> Today's -next fails to build an arm64 allmodconfig and defconfig due to:
>
>> 	arm64-allmodconfig
>> 	arm64-defconfig
>> ERROR (phandle_references): Reference to non-existent node or label "pwm_f_clk_pins"
>> ERROR (phandle_references): Reference to non-existent node or label "pwm_ao_a_3_pins"
>> ERROR: Input tree has errors, aborting (use -f to force output)
>
> The offending references are in 3224eaca966088b4cf4f1ca3 (ARM64: dts:
> meson-gxl: add support for the Khadas VIM board), there doesn't seem to
> be anything providing those phandles in either mainline or -next.

This was my fault, I backed it out soon after I committed, but it was
picked up by -next before I removed it.

Sorry for the noise,

Kevin

  reply	other threads:[~2017-03-23 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23  7:56 next-20170323 build: 2 failures 4 warnings (next-20170323) Build bot for Mark Brown
2017-03-23 11:02 ` Mark Brown
2017-03-23 11:02   ` Mark Brown
2017-03-23 15:44   ` Kevin Hilman [this message]
2017-03-23 15:44     ` Kevin Hilman

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=m2a88cm20o.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=narmstrong@baylibre.com \
    /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.