From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: Build regressions/improvements in v5.18-rc6B
Date: Mon, 9 May 2022 11:13:36 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2205091113010.840289@ramsan.of.borg> (raw)
In-Reply-To: <20220509084005.4133902-1-geert@linux-m68k.org>
On Mon, 9 May 2022, Geert Uytterhoeven wrote:
> JFYI, when comparing v5.18-rc6[1] to v5.18-rc5[3], the summaries are:
> - build errors: +1/-0
+ /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
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/c5eb0a61238dd6faf37f58c9ce61c9980aaffd7a/ (131 out of 138 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/672c0c5173427e6b3e2a9bbb7be51ceeec78093a/ (all 138 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-05-09 9:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 21:09 Linux 5.18-rc6 Linus Torvalds
2022-05-09 8:40 ` Build regressions/improvements in v5.18-rc6 Geert Uytterhoeven
2022-05-09 9:13 ` Geert Uytterhoeven [this message]
2022-05-09 10:47 ` Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6) Regzbot (on behalf of Thorsten Leemhuis)
2022-05-09 17:20 ` Linus Torvalds
2022-05-09 19:04 ` Hans de Goede
2022-05-10 14:41 ` Maarten Lankhorst
2022-05-17 15:50 ` Hans de Goede
2022-05-19 16:09 ` Hans de Goede
2022-05-21 5:01 ` Linus Torvalds
2022-05-21 11:30 ` Thorsten Leemhuis
2022-05-09 23:06 ` Linux 5.18-rc6 Guenter Roeck
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.2205091113010.840289@ramsan.of.borg \
--to=geert@linux-m68k.org \
--cc=linux-crypto@vger.kernel.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).