linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rafael.j.wysocki@intel.com (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20160104 build: 3 failures 15 warnings (next-20160104)
Date: Tue, 5 Jan 2016 02:04:11 +0100	[thread overview]
Message-ID: <568B168B.9060001@intel.com> (raw)
In-Reply-To: <20160104153502.GK16023@sirena.org.uk>

On 1/4/2016 4:35 PM, Mark Brown wrote:
> On Mon, Jan 04, 2016 at 12:12:20PM +0000, Build bot for Mark Brown wrote:
>
> Today's linux-next fails to build for arm64 due to 44d3d051253 (ARM64:
> dts: mt8173: Add CPU OPP, clock and regulator supply properties)

Thanks for letting me know, I've dropped this one.

> in one of Raphael's trees:
>
>> 	arm64-allmodconfig
>> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
>> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
>> 	arm64-defconfig
>> Error: ../arch/arm64/boot/dts/mediatek/mt8173.dtsi:132.24-25 syntax error
> which is failing because at least CLK_INFRA_CA53SEL is used but never
> defined, presumably there is some dependency which wasn't integrated.
> Normally we merge DT changes via the architecture to help avoid these
> issues.

Yes, that would be better.

Thanks,
Rafael

  reply	other threads:[~2016-01-05  1:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1aG3zo-0000gt-2t@optimist>
2016-01-04 15:35 ` next-20160104 build: 3 failures 15 warnings (next-20160104) Mark Brown
2016-01-05  1:04   ` Rafael J. Wysocki [this message]
2016-01-04 16:50 ` Mark Brown
2016-01-04 22:07   ` Arnd Bergmann
2016-01-04 22:44     ` Mark Brown

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=568B168B.9060001@intel.com \
    --to=rafael.j.wysocki@intel.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).