From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org,
Michael Bringmann <mwb@linux.vnet.ibm.com>
Subject: Re: Build regressions/improvements in v4.16-rc2
Date: Mon, 19 Feb 2018 15:03:36 +0100 [thread overview]
Message-ID: <CAMuHMdWs9r4F7FnuHvQGX1L9g91MCepSHroRDhj1tB9E70d5gw@mail.gmail.com> (raw)
In-Reply-To: <1519048647-18732-1-git-send-email-geert@linux-m68k.org>
On Mon, Feb 19, 2018 at 2:57 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> JFYI, when comparing v4.16-rc2[1] to v4.16-rc1[3], the summaries are:
> - build errors: +5/-2
+ /home/kisskb/slave/src/arch/arm64/kernel/head.S: Error: junk at
end of line, first unrecognized character is `U': => 677
+ /home/kisskb/slave/src/arch/arm64/kernel/head.S: Error: missing ')': => 677
+ /home/kisskb/slave/src/arch/arm64/kernel/head.S: Error: unexpected
characters following instruction at operand 2 -- `movk
x1,:abs_g0_nc:0xff00ffffffUL': => 677
+ /home/kisskb/slave/src/arch/arm64/kernel/head.S: Error: unexpected
characters following instruction at operand 2 -- `movz
x1,:abs_g1_s:0xff00ffffffUL': => 677
arm64-allnoconfig
arm64-allmodconfig
arm64-defconfig
(patch available)
+ error: hotplug-cpu.c: undefined reference to
`timed_topology_update': => .text+0x410), .text+0x138)
ppc64le/pseries_le_defconfig+NO_NUMA
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
parent reply other threads:[~2018-02-19 14:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1519048647-18732-1-git-send-email-geert@linux-m68k.org>]
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=CAMuHMdWs9r4F7FnuHvQGX1L9g91MCepSHroRDhj1tB9E70d5gw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mwb@linux.vnet.ibm.com \
/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).