From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: sparclinux@vger.kernel.org
Subject: Re: Build regressions/improvements in v5.18-rc3
Date: Tue, 19 Apr 2022 09:26:03 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2204190925230.302265@ramsan.of.borg> (raw)
In-Reply-To: <20220419072058.4015664-1-geert@linux-m68k.org>
On Tue, 19 Apr 2022, Geert Uytterhoeven wrote:
> JFYI, when comparing v5.18-rc3[1] to v5.18-rc2[3], the summaries are:
> - build errors: +3/-6
+ /kisskb/src/arch/sparc/include/asm/cacheflush_32.h: error: 'struct page' declared inside parameter list will not be visible outside of this definition or declaration [-Werror]: => 38:37
sparc64/sparc-allmodconfig
sparc64-gcc11/sparc-allmodconfig
+ /kisskb/src/crypto/blake2b_generic.c: error: the frame size of 2288 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]: => 109:1
sparc64-gcc11/sparc-allmodconfig
+ /kisskb/src/sound/oss/dmasound/dmasound_core.c: error: 'dmasound_setup' defined but not used [-Werror=unused-function]: => 1431:12
m68k-gcc8/m68k-defconfig
m68k-gcc8/m68k-allmodconfig
m68k-gcc11/m68k-defconfig
m68k-gcc11/m68k-allmodconfig
Fix available
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/b2d229d4ddb17db541098b83524d901257e93845/ (all 96 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e/ (all 96 configs)
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
next prev parent reply other threads:[~2022-04-19 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 21:19 Linux 5.18-rc3 Linus Torvalds
2022-04-18 0:50 ` Guenter Roeck
2022-04-19 7:20 ` Build regressions/improvements in v5.18-rc3 Geert Uytterhoeven
2022-04-19 7:26 ` Geert Uytterhoeven [this message]
2022-04-19 14:24 ` Randy Dunlap
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.2204190925230.302265@ramsan.of.borg \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).