From: Mark Brown <broonie@kernel•org>
To: Catalin Marinas <catalin.marinas@arm•com>,
Will Deacon <will.deacon@arm•com>,
Marc Zyngier <marc.zyngier@arm•com>,
Christoffer Dall <christoffer.dall@linaro•org>
Cc: kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
kvmarm@lists•cs.columbia.edu,
linux-arm-kernel@lists•infradead.org
Subject: Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
Date: Mon, 22 Feb 2016 19:08:32 +0900 [thread overview]
Message-ID: <20160222100832.GX18327@sirena.org.uk> (raw)
In-Reply-To: <E1aXlz4-000486-Pb@optimist>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On Mon, Feb 22, 2016 at 08:36:46AM +0000, Build bot for Mark Brown wrote:
Today's -next fails to build on arm64 due to:
> arm64-allnoconfig
> ../arch/arm64/include/asm/kvm_host.h:338:2: error: implicit declaration of function 'kvm_call_hyp' [-Werror=implicit-function-declaration]
>
> arm64-allmodconfig
> ../arch/arm64/include/asm/kvm_host.h:338:2: error: implicit declaration of function 'kvm_call_hyp' [-Werror=implicit-function-declaration]
> arm64-defconfig
> ../arch/arm64/include/asm/kvm_host.h:338:2: error: implicit declaration of function 'kvm_call_hyp' [-Werror=implicit-function-declaration]
triggered by the merge of the kvm-arm tree with -next today, it looks
like changes in that tree and arm64 aren't playing nicely with each
other (bisect came down to the merge and visual inspection of the
changes didn't immediately show anything else though the issue is
obvious in the code).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-02-22 10:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 8:36 next-20160222 build: 5 failures 9 warnings (next-20160222) Build bot for Mark Brown
2016-02-22 10:08 ` Mark Brown [this message]
2016-02-22 10:41 ` Marc Zyngier
2016-02-22 11:52 ` Brian Starkey
2016-02-22 12:00 ` Marc Zyngier
2016-02-22 12:07 ` Brian Starkey
2016-02-22 12:44 ` Marc Zyngier
2016-02-22 13:19 ` Stephen Rothwell
2016-02-24 3:28 ` Mark Brown
2016-02-24 3:48 ` Stephen Rothwell
2016-02-24 4:16 ` Mark Brown
2016-02-22 10:19 ` Mark Brown
2016-02-22 10:25 ` Mark Brown
2016-02-22 10:37 ` Jean-Philippe Brucker
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=20160222100832.GX18327@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=christoffer.dall@linaro$(echo .)org \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=kvmarm@lists$(echo .)cs.columbia.edu \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marc.zyngier@arm$(echo .)com \
--cc=will.deacon@arm$(echo .)com \
/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