From: Mark Brown <broonie@kernel•org>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel•com>,
Pi-Cheng Chen <pi-cheng.chen@linaro•org>,
Viresh Kumar <viresh.kumar@linaro•org>,
Olof Johansson <olof@lixom•net>, Arnd Bergmann <arnd@arndb•de>
Cc: 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-20160104 build: 3 failures 15 warnings (next-20160104)
Date: Mon, 4 Jan 2016 15:35:02 +0000 [thread overview]
Message-ID: <20160104153502.GK16023@sirena.org.uk> (raw)
In-Reply-To: <E1aG3zo-0000gt-2t@optimist>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
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) 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-01-04 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 12:12 next-20160104 build: 3 failures 15 warnings (next-20160104) Build bot for Mark Brown
2016-01-04 15:35 ` Mark Brown [this message]
2016-01-05 1:04 ` Rafael J. Wysocki
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=20160104153502.GK16023@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=olof@lixom$(echo .)net \
--cc=pi-cheng.chen@linaro$(echo .)org \
--cc=rafael.j.wysocki@intel$(echo .)com \
--cc=viresh.kumar@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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