From: Andy Gross <agross@codeaurora.org>
To: Mark Brown <broonie@kernel.org>
Cc: David Brown <davidb@codeaurora.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Lina Iyer <lina.iyer@linaro.org>,
kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org
Subject: Re: next-20150807 build: 2 failures 51 warnings (next-20150807)
Date: Fri, 7 Aug 2015 12:30:31 -0500 [thread overview]
Message-ID: <20150807173031.GA25070@qualcomm.com> (raw)
In-Reply-To: <20150807122344.GT20873@sirena.org.uk>
On Fri, Aug 07, 2015 at 01:23:44PM +0100, Mark Brown wrote:
> On Fri, Aug 07, 2015 at 01:15:20PM +0100, Build bot for Mark Brown wrote:
>
> Today's linux-next fails to build an arm64 allmodconfig with:
>
> > arm64-allmodconfig
> > ../drivers/firmware/qcom_scm-32.c:27:28: fatal error: asm/outercache.h: No such file or directory
>
> This header file only exists on ARM, either the driver shouldn't be
> built for ARMv8, we need a dummy header for ARMv8 or we need to use the
> header conditionally in the driver.
Right. We're right in the middle of pulling together SCM for 64 bit. I think
for now, perhaps I should just send in a stubbed out placeholder for ARMV8 SCM
and then fill it in once we get that patch set reworked (previously sent by
Kumar Gala).
I'll add that to my branch today and it should resolve our next builds. I'll
send it to arm/soc in a fixes pull request.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-08-07 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 12:15 next-20150807 build: 2 failures 51 warnings (next-20150807) Build bot for Mark Brown
2015-08-07 12:23 ` Mark Brown
2015-08-07 17:30 ` Andy Gross [this message]
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=20150807173031.GA25070@qualcomm.com \
--to=agross@codeaurora.org \
--cc=broonie@kernel.org \
--cc=davidb@codeaurora.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=lina.iyer@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=sboyd@codeaurora.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).