From: agross@codeaurora.org (Andy Gross)
To: linux-arm-kernel@lists.infradead.org
Subject: master build: 1 failures 68 warnings (v4.3-rc2-16-gac2fc4b)
Date: Wed, 23 Sep 2015 11:42:25 -0500 [thread overview]
Message-ID: <20150923164225.GA14209@qualcomm.com> (raw)
In-Reply-To: <20150922161832.GH30445@sirena.org.uk>
On Tue, Sep 22, 2015 at 09:18:32AM -0700, Mark Brown wrote:
> On Tue, Sep 22, 2015 at 08:41:25AM +0100, Build bot for Mark Brown wrote:
>
> Mainline is still failing to build an arm64 allmodconfig due to:
>
> > arm64-allmodconfig
> > ../drivers/firmware/qcom_scm-32.c:196:4: error: expected string literal before '__asmeq'
> > ../drivers/firmware/qcom_scm-32.c:221:2: error: implicit declaration of function 'secure_flush_area' [-Werror=implicit-function-declaration]
> > ../drivers/firmware/qcom_scm-32.c:239:2: error: implicit declaration of function 'outer_inv_range' [-Werror=implicit-function-declaration]
> > ../drivers/firmware/qcom_scm-32.c:331:4: error: expected string literal before '__asmeq'
> > ../drivers/firmware/qcom_scm-32.c:361:4: error: expected string literal before '__asmeq'
>
> which has been the case since before -rc1. There was a patch posted for
> this by Andy Gross (firmware: qcom: scm: Add function stubs for ARM64)
> which got positively reviewed - where are we with getting that merged
> into mainline?
V2 of the patch is out and reviewed by Russell and Bjorn. I have it in next
right now. I'll resend my pull shortly.
--
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-09-23 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1ZeICY-00014h-E8@optimist>
2015-09-22 16:18 ` master build: 1 failures 68 warnings (v4.3-rc2-16-gac2fc4b) Mark Brown
2015-09-23 16:42 ` 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=20150923164225.GA14209@qualcomm.com \
--to=agross@codeaurora.org \
--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 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.