mirror of https://lore.kernel.org/lkml/
 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-rc8
Date: Sun, 18 Apr 2021 19:06:37 -0700	[thread overview]
Message-ID: <20210419020637.GA145376@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wjgVFDhX60fxwDobHoqJvVkuxf=JgSTtGnGMa5r-1u4Yw@mail.gmail.com>

On Sun, Apr 18, 2021 at 03:02:49PM -0700, Linus Torvalds wrote:
> Ok, so it's been _fairly_ calm this past week, but it hasn't been the
> kind of dead calm I would have taken to mean "no rc8 necessary".
> 
> So here we are, with an extra rc to make sure things are all settled
> down. It's not _that_ rare: this is the fifth time in the 5.x series
> we've ended up with an rc8, but I have to admit that I prefer it when
> a release doesn't end up needing that extra week.
> 
> Because let's keep it to just one extra week, ok? We have occasionally
> done rc9's too, but I really don't expect that this time around.
> 
> About half of this is once more networking, with driver and bpf
> verifier fixes standing out. Other than that it's mostly other driver
> updates (gpu, dmaengine, HID, input, nvdimm) and arch updates (mainly
> arm and arm64).
> 
> And a number of one-liner build fixes for unusual configurations.
> 
> So it's not tiny, but it's all small enough that you can easily scan
> through the shortlog below and get a fair sense of what's going on.
> 
> Let's plan on a final 5.12 release next weekend - but please do give
> it one last test to check that it is all solid. Ok?
> 

Build results:
	total: 151 pass: 151 fail: 0
Qemu test results:
	total: 461 pass: 461 fail: 0

Guenter

      reply	other threads:[~2021-04-19  2:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-18 22:02 Linus Torvalds
2021-04-19  2:06 ` 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=20210419020637.GA145376@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

all inboxes | Powered by JetHome®