linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Date: Sun, 25 Apr 2021 17:00:23 -0700	[thread overview]
Message-ID: <20210426000023.GA116328@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wj3ANm8QrkC7GTAxQyXyurS0_yxMR3WwjhD9r7kTiOSTw@mail.gmail.com>

On Sun, Apr 25, 2021 at 02:06:35PM -0700, Linus Torvalds wrote:
> Thanks to everybody who made last week very calm indeed, which just
> makes me feel much happier about the final 5.12 release.
> 
> Both the shortlog (appended) and the diffstat are absolutely tiny, and
> it's mainly just a random collection of small fixes in various areas:
> arm64 devicetree files, some x86 perf event fixes (and a couple of
> tooling ones), various minor driver fixes (amd and i915 gpu fixes
> stand out, but honestly, that's not because they are big, but because
> the rest is even smaller), a couple of small reverts, and a few
> locking fixes (one kvm serialization fix, one memory ordering fix for
> rwlocks).
> 
> Anyway, this obviously means that I'll start the merge window for 5.13
> tomorrow. But I'd ask that even developers champing at the bit to get
> their shiny new code merged please spend a bit of time running and
> checking out 5.12.
> 
> Despite the extra week, this was actually a fairly small release
> overall.  Judging by linux-next, 5.13 will be making up for it.
> 

I wonder if it makes sense to report the status of -next at the beginning
of a commit window on a regular basis.

For next-20210423:

Build results:
	total: 151 pass: 149 fail: 2
Failed builds:
	csky:tinyconfig
	mips:allnoconfig
Qemu test results:
	total: 461 pass: 440 fail: 21
Failed tests:
	arm:raspi2:multi_v7_defconfig:net,usb:bcm2836-rpi-2-b:initrd
	arm:raspi2:multi_v7_defconfig:sd:net,usb:bcm2836-rpi-2-b:rootfs
	mipsel:mips32r6-generic:malta_32r6_defconfig:nocd:smp:net,pcnet:ide:rootfs
	<all riscv32>

Let's see how many of those problems find their way into mainline.

Guenter

  parent reply	other threads:[~2021-04-26  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25 21:06 Linux 5.12 Linus Torvalds
2021-04-25 23:55 ` Guenter Roeck
2021-04-26  0:00 ` Guenter Roeck [this message]
2021-04-26  2:26 ` Ken Moffat

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=20210426000023.GA116328@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).