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.12-rc6
Date: Mon, 5 Apr 2021 10:10:11 -0700 [thread overview]
Message-ID: <20210405171011.GA72391@roeck-us.net> (raw)
In-Reply-To: <CAHk-=whK9=wafv+cSLCGqFGPBbgp67Dut3jKCnWB--8y7Lxonw@mail.gmail.com>
On Sun, Apr 04, 2021 at 02:30:58PM -0700, Linus Torvalds wrote:
> Well, if rc5 was bigger than usual, and I worried about what that
> meant for this release, rc6 is positively tiny.
>
> So I think it was just due to the usual random timing fluctuations,
> probably mainly networking updates (which were in rc5, but not in
> rc6). Which means that unless things change in the next two weeks, the
> schedule for this release is going to be the usual one.
>
> Most of the changes here are drivers (gpu and usb stand out, that's
> not because of any huge changes, it's mainly because everything else
> is even smaller) and some arch updates (mainly x86 kvm, but some
> arm64, powerpc, s390, xtensa and RISC-V too).
>
> The rest is random other stuff (with io_uring showing up again, but
> much smaller this time).
>
> The shortlog is appended - small and easy to scan if you care about the details.
>
> So hey, in between all those extra helpings of memma - it is Easter,
> after all - go ahead and do some more testing as we approach the final
> weeks of the release,
>
No change in test results since last week, except that I added a number
of network interface sanity tests which all pass.
Build results:
total: 151 pass: 151 fail: 0
Qemu test results:
total: 460 pass: 459 fail: 1
Failed tests:
openrisc:or1ksim_defconfig
Guenter
next prev parent reply other threads:[~2021-04-05 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 21:30 Linux 5.12-rc6 Linus Torvalds
2021-04-05 17:10 ` Guenter Roeck [this message]
2021-04-05 17:14 ` Linus Torvalds
2021-04-05 17:28 ` Guenter Roeck
2021-04-05 22:29 ` Frank Rowand
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=20210405171011.GA72391@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 read-only IMAP folder(s) and NNTP newsgroup(s).