archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <>
To: Linus Torvalds <>
Cc: Linux Kernel Mailing List <>
Subject: Re: Linux 5.12-rc5
Date: Sun, 28 Mar 2021 19:07:46 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, Mar 28, 2021 at 04:05:54PM -0700, Linus Torvalds wrote:
> So if rc4 was perhaps a bit smaller than average, it looks like rc5 is
> a bigger than average.  We're not breaking any records, but it
> certainly isn't tiny, and the rc's aren't shrinking.
> I'm not overly worried yet, but let's just say that the trend had
> better not continue, or I'll start feeling like we will need to make
> this one of those releases that need an rc8.
> Most of the changes are drivers (gpu and networking stand out, but
> there's various other smaller driver updates elsewhere too) with core
> networking (including bpf) fixes being another noticeable subsystem.
> Other than that, there's a smattering of noise all over: minor arch
> fixes, some filesystem fixes (btrfs, cifs, squashfs), selinux, perf
> tools, documentation.
> io_uring continues to have noise in it, this time mainly due to some
> signal handling fixes. That removed a fair amount of problematic
> special casing, but the timing certainly isn't great.
> So again, nothing really scary, just rather more than I would have
> liked to have in an rc5.
> Shortlog appended for people who want to delve into the details,

Build results:
	total: 151 pass: 151 fail: 0
Qemu test results:
	total: 458 pass: 457 fail: 1
Failed tests:

This is not really a new problem. I enabled devicetree unit tests
in the openrisc kernel and was rewarded with a crash.
has all the glorious details.


  reply	other threads:[~2021-03-29  2:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28 23:05 Linus Torvalds
2021-03-29  2:07 ` Guenter Roeck [this message]
2021-03-29 18:05   ` Linus Torvalds
2021-03-29 18:41     ` Rob Herring
2021-03-29 19:04       ` Frank Rowand
2021-03-29 19:42     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: Linux 5.12-rc5' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).