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.13-rc4
Date: Wed, 2 Jun 2021 04:44:57 -0700 [thread overview]
Message-ID: <20210602114457.GA2899409@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wjKJ5Mw7P=U0AyhFJbGB+4TT=SE=tmf=md0cqEn527HFg@mail.gmail.com>
On Sun, May 30, 2021 at 12:19:14PM -1000, Linus Torvalds wrote:
> So after two small rc releases, the other show finally dropped, and
> rc4 is fairly sizable.
>
> It's not the biggest rc4 we've ever had, but it's certainly up there,
> believably competing for the title.
>
> That said, exactly because of the calm rc2 and rc3, the size of rc4
> doesn't worry me, and I think the 5.13 release looks fairly normal.
> This bump is just because we had some stable work finally hit my tree.
> Notably the networking tree, but there's a lot of driver tree fixes
> too.
>
> The fixes are fairly spread out, and mostly small. Some of the bigger
> chunks are for new self tests (both bpf and kvm), and outside of those
> new tests the diffstat looks nice and flat (ie lots of smaller changes
> rather than big peaks). Networking (both core and drivers) does stand
> out, but there are filesystem fixes too (xfs, nfs, cifs), various
> random driver subsystems (sound, i2c, tty, usb, iio, scsi, spi..). And
> some arch updates (mostly kvm-related, but small arm64, s390, MIPS
> fixes - and some powerpc perf event descriptions too).
>
> Please do go test, and let's make sure 5.13 is solid.
>
Build results:
total: 151 pass: 151 fail: 0
Qemu test results:
total: 462 pass: 462 fail: 0
Guenter
prev parent reply other threads:[~2021-06-02 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 22:19 Linux 5.13-rc4 Linus Torvalds
2021-06-02 11:44 ` 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=20210602114457.GA2899409@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).