Re: Build regressions/improvements in v4.3-rc1
From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: 2015-09-13 20:23:51
Also in:
linux-arm-kernel, lkml
On Sun, Sep 13, 2015 at 5:19 PM, Guenter Roeck [off-list ref] wrote:
On Sun, Sep 13, 2015 at 11:03:51AM +0200, Geert Uytterhoeven wrote:quoted
On Sun, Sep 13, 2015 at 11:01 AM, Geert Uytterhoeven [off-list ref] wrote:quoted
Below is the list of build error/warning regressions/improvements in v4.3-rc1[1] compared to v4.2[2].[ ... ]quoted
quoted
+ /home/kisskb/slave/src/arch/powerpc/kvm/book3s_pr.c: error: 'last_=
sc' may be used uninitialized in this function [-Werror=3Duninitialized]: = =3D> 1094:31
quoted
powerpc-allyesconfig, powerpc-randconfig, powerpc-allmodconfigI think that only affects powerpc-randconfig.
Right, on powerpc-all{mod,yes}config it's just a build warning, not an erro=
r.
arm64:allmodconfig: drivers/firmware/qcom_scm-32.c:196:4: error: expected string literal befo=
re =E2=80=98__asmeq=E2=80=99
drivers/firmware/qcom_scm-32.c:221:2: error: implicit declaration of func=
tion =E2=80=98secure_flush_area=E2=80=99
drivers/firmware/qcom_scm-32.c:239:2: error: implicit declaration of func=
tion =E2=80=98outer_inv_range=E2=80=99
drivers/firmware/qcom_scm-32.c:331:4: error: expected string literal befo=
re =E2=80=98__asmeq=E2=80=99
drivers/firmware/qcom_scm-32.c:361:4: error: expected string literal befo=
re =E2=80=98__asmeq=E2=80=99
Time for kisskb to gain arm64 support?
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. Bu=
t
when I'm talking to journalists I just say "programmer" or something like t=
hat.
-- Linus Torvalds