From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: Build failure on arm64 defconfig for linux-next recently
Date: Fri, 23 Feb 2018 12:59:16 +0000 [thread overview]
Message-ID: <20180223125916.k2yp7bfes2lrnwrb@armageddon.cambridge.arm.com> (raw)
In-Reply-To: <0cd1b5a5-820a-3984-01b5-141770adbbea@arm.com>
On Fri, Feb 23, 2018 at 11:54:19AM +0000, Robin Murphy wrote:
> On 23/02/18 08:03, Shawn Lin wrote:
> > I failed to build the arm64 kernel for linux-20180222 and I confirm it
> > works for linux-20180206. It seems there was some patches for head.S
> > got merged. Is it a known issue? Or a fix is coming?
>
> Yes, I broke it, sorry!
>
> There's a fix queued in arm64/fixes/core already (04c4927359b1). Using a
> different toolchain is another option, since the one I'm currently using
> (gcc-linaro-7.2.1-2017.11) builds it just fine, which is how I managed to
> create this mess in the first place ;)
Pull request to go out today. I forgot that arm64 fixes/core doesn't get
pulled into -next (maybe we should fix this).
--
Catalin
next prev parent reply other threads:[~2018-02-23 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 8:03 Build failure on arm64 defconfig for linux-next recently Shawn Lin
2018-02-23 11:54 ` Robin Murphy
2018-02-23 12:59 ` Catalin Marinas [this message]
2018-02-23 14:23 ` Shawn Lin
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=20180223125916.k2yp7bfes2lrnwrb@armageddon.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--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.