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.15-rc3
Date: Mon, 27 Sep 2021 04:05:48 -0700	[thread overview]
Message-ID: <20210927110548.GA771805@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wgoE8XBPVA6Mu4CygxX9TE0FgWaAsVUJOe8KQH-CzEcAA@mail.gmail.com>

On Sun, Sep 26, 2021 at 02:21:52PM -0700, Linus Torvalds wrote:
> So after a somewhat rocky merge window and second rc, things are now
> actually looking pretty normal for rc3. Knock wood.
> 
> There are fixes all over, and the statistics look fairly regular, with
> drivers dominating as they should (since they are most of the tree).
> And outside of drivers, we have a fairly usual mix of changes -
> architecture fixes, networking, filesystems, and tooling (the latter
> being mostly kvm selftests).
> 
> Shortlog appended, it's not too long and easy to scan through to get a
> flavor for the details if you happen to care.
> 
> Please do give it a whirl,
> 

Build results:
	total: 153 pass: 152 fail: 1
Failed builds:
	mips:allmodconfig
Qemu test results:
	total: 480 pass: 479 fail: 1
Failed tests:
	sparc64:sun4u:nodebug:smp:virtio-pci:net,i82559er:hd

Almost there ...

Guenter

  reply	other threads:[~2021-09-27 11:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26 21:21 Linux 5.15-rc3 Linus Torvalds
2021-09-27 11:05 ` Guenter Roeck [this message]
2021-09-27 18:55   ` Linus Torvalds
2021-09-27 20:09     ` Thomas Bogendoerfer
2021-09-27 20:46       ` Linus Torvalds
2021-09-30 13:42         ` Guenter Roeck
2021-09-27 22:31     ` Michael S. Tsirkin
2021-09-27 20:48 Sedat Dilek
2021-09-27 21:47 ` Jason Gunthorpe
2021-09-27 21:48   ` Nick Desaulniers
2021-09-27 21:49   ` Sedat Dilek
2021-10-01 15:44   ` Sedat Dilek

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=20210927110548.GA771805@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).