From: Michael Ellerman <mpe@ellerman.id.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Build regressions/improvements in v4.3-rc1
Date: Mon, 14 Sep 2015 15:19:46 +1000 [thread overview]
Message-ID: <1442207986.8149.0.camel@ellerman.id.au> (raw)
In-Reply-To: <CAMuHMdVGEDKFxD7wf6ZOAGiOByM5c0Awx-anLsYGLQHV1yJW+w@mail.gmail.com>
On Sun, 2015-09-13 at 22:23 +0200, Geert Uytterhoeven wrote:
> On Sun, Sep 13, 2015 at 5:19 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> > 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’
> > drivers/firmware/qcom_scm-32.c:239:2: error: implicit declaration of function ‘outer_inv_range’
> > 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’
>
> Time for kisskb to gain arm64 support?
Yes. I'll add it to my TODO list.
cheers
prev parent reply other threads:[~2015-09-14 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1442134868-17607-1-git-send-email-geert@linux-m68k.org>
2015-09-13 9:03 ` Build regressions/improvements in v4.3-rc1 Geert Uytterhoeven
2015-09-13 15:19 ` Guenter Roeck
2015-09-13 16:57 ` Russell King - ARM Linux
2015-09-14 1:32 ` Guenter Roeck
2015-09-13 20:23 ` Geert Uytterhoeven
2015-09-14 5:19 ` Michael Ellerman [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=1442207986.8149.0.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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).