From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.18-rc4
Date: Mon, 25 Apr 2022 08:03:56 -0700 [thread overview]
Message-ID: <20220425150356.GA4138752@roeck-us.net> (raw)
In-Reply-To: <CAHk-=whmtHMzjaVUF9bS+7vE_rrRctcCTvsAeB8fuLYcyYLN-g@mail.gmail.com>
On Sun, Apr 24, 2022 at 03:22:59PM -0700, Linus Torvalds wrote:
> Fairly slow and calm week - which makes me just suspect that the other
> shoe will drop at some point.
>
> But maybe things are just going really well this release. It's bound
> to happen _occasionally_, after all.
>
> It's not only a fairly small set of commits, the diffstat is pretty
> small and flat too. The biggest single patch is literally killing off
> a zombie file that had already been deleted - well, renamed, really -
> once, but it didn't know to stay dead, and was resurrected by a merge
> mistake.
>
> The changes are sprinkled all over, they just aren't all that big:
> arch updates (sound being the bulk of it, but "bulk" really is fairly
> misleading), some driver updates, a couple of filesystem fixes, memory
> management, networking, and some tooling (mainly a couple of
> selftests).
>
Build results:
total: 151 pass: 131 fail: 20
Failed builds:
arm:allnoconfig
arm:tinyconfig
h8300:allnoconfig
h8300:tinyconfig
h8300:edosk2674_defconfig
h8300:h8300h-sim_defconfig
h8300:h8s-sim_defconfig
m68k:allnoconfig
m68k:tinyconfig
m68k_nommu:m5272c3_defconfig
m68k_nommu:m5307c3_defconfig
m68k_nommu:m5249evb_defconfig
m68k_nommu:m5407c3_defconfig
riscv32:allnoconfig
riscv32:tinyconfig
riscv:allnoconfig
riscv:tinyconfig
s390:allmodconfig
sh:allnoconfig
sh:tinyconfig
Qemu test results:
total: 489 pass: 486 fail: 3
Failed tests:
arm:mps2-an385:mps2_defconfig:mps2-an385:initrd
mcf5208evb:m5208:m5208evb_defconfig:initrd
xtensa:de212:kc705-nommu:nommu_kc705_defconfig
As far as I can see this is all due to
error: page_alloc.c: undefined reference to `vmalloc_huge'
as already reported.
Guenter
next prev parent reply other threads:[~2022-04-25 15:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 22:22 Linus Torvalds
2022-04-25 7:32 ` Build regressions/improvements in v5.18-rc4 Geert Uytterhoeven
2022-04-25 7:42 ` Geert Uytterhoeven
2022-04-25 9:50 ` Linux 5.18-rc4 Sudip Mukherjee
2022-04-25 21:27 ` Andrew Morton
2022-04-25 21:42 ` Linus Torvalds
2022-04-25 15:03 ` Guenter Roeck [this message]
2022-04-27 17:59 ` Ammar Faizi
2022-04-27 18:31 ` Linus Torvalds
[not found] ` <87r1414y5v.fsf@email.froward.int.ebiederm.org>
2022-06-06 18:28 ` Linus Torvalds
2022-06-06 19:19 ` John Johansen
2022-06-06 19:47 ` Linus Torvalds
2022-06-06 20:23 ` Matthew Wilcox
2022-06-06 21:00 ` John Johansen
2022-06-13 22:48 ` Matthew Wilcox
2022-06-21 20:27 ` John Johansen
2022-07-13 9:37 ` Ammar Faizi
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=20220425150356.GA4138752@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome