From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: nvdimm@lists.linux.dev, Kees Cook <keescook@chromium.org>,
linux-scsi@vger.kernel.org, linux-sh@vger.kernel.org,
linux-xtensa@linux-xtensa.org, linux-um@lists.infradead.org,
sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: Build regressions/improvements in v5.19-rc1
Date: Mon, 6 Jun 2022 11:08:11 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2206061104510.695137@ramsan.of.borg> (raw)
In-Reply-To: <20220606082201.2792145-1-geert@linux-m68k.org>
On Mon, 6 Jun 2022, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v5.19-rc1[1] compared to v5.18[2].
>
> Summarized:
> - build errors: +9/-10
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/f2906aa863381afb0015a9eb7fefad885d4e5a56/ (all 135 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/4b0986a3613c92f4ec1bdc7f60ec66fea135991f/ (131 out of 135 configs)
> 9 error regressions:
> + /kisskb/src/arch/um/include/asm/page.h: error: too few arguments to function 'to_phys': => 105:20
> + /kisskb/src/drivers/nvdimm/pmem.c: error: conflicting types for 'to_phys': => 48:20
> + /kisskb/src/drivers/nvdimm/pmem.c: error: control reaches end of non-void function [-Werror=return-type]: => 324:1
um-x86_64/um-allyesconfig
> + /kisskb/src/arch/xtensa/kernel/entry.S: Error: unknown pseudo-op: `.bss': => 2176
xtensa-gcc11/xtensa-allmodconfig
> + /kisskb/src/drivers/tty/serial/sh-sci.c: error: unused variable 'sport' [-Werror=unused-variable]: => 2655:26
sh4-gcc11/se7619_defconfig
sh4-gcc11/sh-allmodconfig
Fix available
https://lore.kernel.org/all/4ed0a7a0d3fa912a5b44c451884818f2c138ef42.1644914600.git.geert+renesas@glider.be
> + /kisskb/src/include/linux/fortify-string.h: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning]: => 344:25
powerpc-gcc11/ppc64_book3e_allmodconfig
> + /kisskb/src/include/ufs/ufshci.h: error: initializer element is not constant: => 245:36
mipsel-gcc5/mips-allmodconfig
powerpc-gcc5/powerpc-allmodconfig
FTR, include/ufs/ufshci.h lacks a MAINTAINERS entry.
> + error: relocation truncated to fit: R_SPARC_WDISP22 against `.init.text': => (.head.text+0x5100), (.head.text+0x5040)
> + error: relocation truncated to fit: R_SPARC_WDISP22 against symbol `leon_smp_cpu_startup' defined in .text section in arch/sparc/kernel/trampoline_32.o: => (.init.text+0xa4)
sparc64-gcc5/sparc-allmodconfig
> 3 warning regressions:
> + arch/m68k/configs/multi_defconfig: warning: symbol value 'm' invalid for ZPOOL: => 61
> + arch/m68k/configs/sun3_defconfig: warning: symbol value 'm' invalid for ZPOOL: => 37
Will be fixed by the m68k defconfig update for v5.20.
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:[~2022-06-06 9:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220606082201.2792145-1-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=alpine.DEB.2.22.394.2206061104510.695137@ramsan.of.borg \
--to=geert@linux-m68k.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nvdimm@lists.linux.dev \
--cc=sparclinux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox