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-rc6
Date: Mon, 9 May 2022 16:06:36 -0700 [thread overview]
Message-ID: <20220509230636.GA1551031@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wi0vqZQUAS67tBsJQW+dtt89m+dqA-Z4bOs8CH-mm8u2w@mail.gmail.com>
On Sun, May 08, 2022 at 02:09:27PM -0700, Linus Torvalds wrote:
> So 5.18 is looking like it's going to be one of the larger releases in
> numbers of commits (we'll see where it ends up - it's going to be
> neck-and-neck with 5.14 right now, but won't be as big as 5.13 was).
> But despite the merge window being big, the release candidates have
> generally been quite modest in size, and rc6 continues that trend. I
> keep expecting the other shoe to drop, but 5.18 just seems to be quite
> well-behaved.
>
> Let's see if this jinxes it, but nothing looks particularly scary
> here. rc6 looks to be mostly some driver updates (network drivers and
> rdma stand out, small random fixes elsewhere), with the usual
> smattering of architecture updates (x86 kvm fixes, but also a
> long-standing x86 kernel FP use issue, and a smattering of parisc and
> powerpc fixes). And some wireguard selftest updates.
>
> The rest is mostly some btrfs fixes, some core networking, and just
> random small one-offs elsewhere.
>
> Please do go test it all out - because things may look good now, but
> continued testing is the only thing that will make sure.
>
Build results:
total: 151 pass: 151 fail: 0
Qemu test results:
total: 489 pass: 489 fail: 0
... and even the parisc warning is gone now.
Guenter
prev parent reply other threads:[~2022-05-09 23:06 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 ` Build regressions/improvements in v5.18-rc6B Geert Uytterhoeven
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 ` Guenter Roeck [this message]
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=20220509230636.GA1551031@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;
as well as URLs for NNTP newsgroup(s).